244 karma · joined March 7, 2016
I use UTM to run Debian 11 ARM. The update-binfmts command is absolutely magical, docker images will happily run both arm and x86 binaries.
Battery lasts all day and the machine stays ice-cold.
Edit: It does in-fact load a JSON payload along with client-side routing as well if you click to view comments. But then if you use browser refresh, it renders as a traditional server-side request. So true to its name, Remix is a blend of both approaches, playing on the strengths of each.
Man I spent endless hours playing and coding back then. But I never could get into the later Halos. The gameplay was so drastically different. The CE pistol was the ultimate weapon. It was always available and had the potential to bail you out of any scenario. But you can’t solely rely on it to win competitive games. Powerup timing is king. Everyone knew the exact second overshield/rockets would spawn, so there was a natural flow to the maps as teams pushed to gain these items. Halo 2 and beyond removed all of this.
ANY time ruby 1.8 raised a timeout, it was silently swallowed, and Unicorn returned the adjacent request session_id. We had to constantly defend against any code that might hit the native timeout.
I noticed your personal website mentions building products with React Native, but in this thread you mentioned Gentle was built with Flutter.
It's been a few years since I took a serious look at mobile, and after trying out NativeScript and React Native then, I ended up just wrapping web views. The bar for app experiences is much higher now, and it sounds like you have been able to iterate quickly without compromising quality. Will Flutter be your tool moving forward? Do you give it the upper hand over RN? Or is the difference just personal taste?
But before you have kids, it is more important to find a committed partner. There is nothing that will wreak havoc more on your life than a broken family. If you ever hear a parent regret having kids, you can bet there was trouble with their partner.
I'd like to see a build tool that focuses on plain HTML, CSS, and ES6 modules. It takes the input .html file, parses the <script type="module"> elements, and statically analyzes the code to polyfill and re-write output for specified browser compatibility.
I think part of the problem is that the intro tutorials for the fully loaded frameworks look so much simpler at a glance than trying to wrangle something on your own.
Any ideas for youmightnotneedreact.com?
The hard part is accepting that this is an ongoing cycle and that you need to find ways to build inertia and continually evolve the value proposition.
I started on your same path, email alerts per bank, but then found it was possible to jump up a level to the payment network using Visa Purchase Alerts. I signed up the alerts to an automated inbox that parses the content for the transaction name, location, amount, and last4. It's working with the first four credit cards I have tried, and I receive the notice generally within seconds.
This works out well for a product targeting U.S. credit card debt. Hopefully MasterCard will follow suit, which is then potentially 100% market coverage, if you can convince a user to signup with an email address of your service.
In 2009, there was around 25 million smart phone users. We will close out this decade close to 3 billion. That is half the world with a geo-location based device in their pocket which grabs their attention for hours each day.
The peak may have been Pokemon Go, or maybe we aren't even there yet.
I used it a few years ago and one of my favorite aspects was using primarily for generating templates server side, and only upgrading to a client component when things became more complex. Out-of-order async rendering was pretty nifty too.
Money talks. I'm sure you can find someone in no time if you advertise $500k in compensation. Most employers balk at that rate, so most of the talent take the freelance/consulting route.
I guess anything Ruby is old news on HN
We use rollup[1] for our production bundle. We manage all 3rd party dependencies by source control. We don't need to rely on NPM for ES5/ES6/CommonJS/AMD/Modules - We have full control of each dependency to use the code that is most fit. Sometimes that is already checked-in by the author, sometimes we need to build it, sometimes we can use the modern ES6 code directly, sometimes we can remove duplicate polyfills already in our bundle.
It takes bit more discipline, but the extra security, optimal build, and peace of mind knowing how things work, are well worth the effort to us.
Vue users are more likely to bypass NPM. They are often on-boarded with the gentler approach most familiar to those who "sprinkle in some jQuery" - Drop in a <script> tag and you are ready to rock. This approach is more likely to use a local file or from CDN.
Or learning that user has a very different meaning of flawless, and that is almost always the more important definition.
This makes things even more confusing. What do we call the former, then? 10x individual contributors are absolutely a reality. It is generally more about horizontal skills and cutting though things to identify what really matters to the business. If you are a ticket taker, your output will be very limited. But if you can read between the lines and understand what stakeholders are _trying_ to do, but are struggling to clearly communicate, and if you can find creative ways to solve larger problems, and gracefully move around priorities in the roadmap, you are very likely worth 10x-100x other team members who may have similar titles.
However, if there is a clear boundary of work accomplished, I break the build with a simple syntax error and avoid thinking about the next task. I can step away from work completely, without any lingering thoughts, and the next time I am back at it, the syntax error helps me jump in right where I left off.
If I have a group of 100 people in a similar physical location, I'd like to be able to have 100 speakers in sync. Requiring them all to create an account, let alone purchase Spotify Premium, is unfortunately too much to ask.
If you have some control over the payment model, I'd even be interested in paying an extra fee as a DJ in order to enable more remote speaker connections.
Seems like there is a greater movement towards the freelance economy, but these things still suck to deal with when you are independent.