Hacker Newsnew | past | comments | ask | show | jobs | submit | madlynormal's commentslogin

Give serious thought about using React Native over Flutter: 1) You can use JavaScript/TypeScript instead of learning another bespoke language (Dart). 2) With React Native you have the option of deploying OTA updates, this allows you to deploy fixes and basic updates without going through the app store review process.


> With React Native you have the option of deploying OTA updates

How is this done? Any documentation, tutorial or example that you can point to?

> this allows you to deploy fixes and basic updates without going through the app store review process.

Does Apple and Google allow this?


They do. With the caveat that only the js bundle can be pushed via ota. If your app changes that touch the native implementation requires a traditional review. Check out Expo publish and Microsoft Codepush.


Flutter has hot reload, does React Native?


It does. The react native metro server will watch for file changes and hot reload the javascript bundle.


What about the Toyota/BWM collaboration on the new Supra?


And the Toyota/Subaru collaboration on the BRZ/FR-S/GT86.


I game with a 2600x / 2080ti @ 1440p/165hz, on average I see 150 FPS in Apex Legends. Not an optimal setup, but not too shabby either. Planning on upgrading to the 3900x once it's released.


Actually, with a BIOS update, the new Zen 2 CPU's are indeed compatible with most x470, b450, and even 300 series motherboards.


Similar experience at the company I work for, though we're mostly using Angular for FE.


Is there a benefit to rebasing vs merging, specifically if your flow is to squash commits before merging back into base?


Most people's aversion to rebase is an aversion to altering history. Since squashing alters history anyway, I'd argue that you might as well just use rebase when you do it.

In a rebase-oriented workflow, every commit has exactly one parent, and the commit history is entirely linearized. Merge commits have more than one parent, which means going backwards through the history means that you have to essentially navigate the branching structure to navigate the history. That makes it pretty hard to do!

A linear history is comparatively easier to reason about than a history with all of its branches. It's also, in a sense, less "true"! So it depends what you care about. Do you care about telling the exact story of everything that happened to everyone on the project, or do you care about the history of changes to the one shared copy?

Linear histories also make it easy to step backwards through the history one commit at a time. I personally just do `get checkout HEAD^` over and over, walking through the history in reverse, since most breakages are noticed within a few commits of their occurrence. I really like being able to do that. A lot of people think that's useless!

If you have one copy of the project that is considered authoritative, and all developers are synchronizing via that single authoritative copy, creating a clean and linear history is possible.


Rebasing picks commits, merging merges. Unless you're actually trying to merge two histories, I don't recommend using merge. Just think about what you're logically trying to accomplish and choose that tool.


This is a great read, not only Software Developers, but also Product Managers, and Owners, who would like a better understanding of the development cycle they're working within.


> Lately I have been building applications in Python/tkinter and I still can't get over how fast it is on both my mac and PC both to start up and when running.

Has the GUI of tkinter apps improved over the past couple of years? I have yet to see an interface built with tk that doesn’t look like it was meant for Win95.


For native looking tkinter, there's ttk (themed tkinter).


I'm always suspicious when people say something can be done. Why isn't it the default then? Because there is some drawback to that choice. But what is it?


haha, well for example there's an issue open since 2012 about how common convenience dialogs don't work with themed tkinter although i don't really understand the comments about IDLE supposedly doing it automatically but not yet?. i think tkinter is a tool you reach for coz you know python only to realize you can't really write bulletproof UI in it coz of some workaround or issue.

https://bugs.python.org/issue15191


I used tkinter a few years ago, since it was available on Raspbian on the Raspberry Pi. It looked bad on Linux, and it seemed tkinter was not in active development or getting a lot of attention. I remember not having found any sane workflow for how to place GUI elements and struggled to place a bunch of text boxes and buttons.

Reasonable or not, I have a hard time accepting workflows worse than what Microsoft Access or VB 6.0 had.


> Is it? Is the $30 puck better than the Home assistant or does it just suck that much more in French than it does in English? (Not being snarky, genuinely asking)

Absolutely it is. In general, my Siri usage is limited to opening Google Assistant, that's how bad it is. Also, "Hey Google" works as a command on most devices.


There are neighborhoods in Queens to consider: Forest Hills, Astoria, Kew Gardens, Long Island City.


I visited a friend of mine when he lived in Astoria ca. 2012-14 or so probably 3 or 4 times, it seemed like a good area and the rent seemed reasonable at the time. He commuted to Columbus Circle and while I never made the trip during rush hour it was not bad at all.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: