matt2000

I appreciate the author putting this post together. I am, however, having trouble squaring the overall positive tone of the piece with what seem like multiple show stopping problems. The bottom line I am taking away from this is you might not be able to ship your app at all if you use SwiftUI. Am I being too harsh? Or does that seem accurate?

I would guess so, although the size overhead for an optimized Flutter release build is now down around ~4MB, so not a determining factor for most use cases anyway.

They are planning to complete the transition in 2 years: https://www.apple.com/newsroom/2020/06/apple-announces-mac-t...

Makes your question even more interesting though, what will a Mac Pro look like running Apple silicon inside 2 years from now?

I love to read about how StackExchange does things, it's such a stark contrast to the cloud maximalists. I'm not saying there aren't advantages to each camp, it's just nice to have a solid example on the "vertical scaling can actually get you pretty damn far" side of things.

Awesome, thanks so much for the info. Glad to hear it's a viable option since the hardware prices always seemed great and the unlimited bandwidth would be key for certain applications too.

Would you mind sharing any of your experiences with OVH that you’re able to? I’ve used them before for hobby projects but was always worried about reliability for anything more serious. Had also heard questionable things about their networking reliability. Anything related to roughly how many machines you run, types, problems encountered, etc would be super helpful. Thanks!

Probably in-house expertise and experience running previous services. That usually (or should at least) outweighs feature set in selection process, especially for databases.

> "Because, as it turns out, a Libertarian free-for-all doesn’t work."

But isn't that how the Internet works? No one "approves" a website for release.

I agree with you. When Swift was introduced it was billed as a modern replacement for ObjC that was easier to learn, even a good choice as a language for learning to program. I'm not sure it was ever that, but it sure isn't now. I just got back into a project written in Swift 3 and had to change a bunch of stuff to get it to work in Swift 5. Why? I keep hearing the language is going to be stable "soon" but that doesn't appear to be happening.

Swift appears to be a language for the captive audience of iOS devs, who are able to keep up if that's all they're doing. I don't really see it being adopted anywhere else.

Side note, if you're exclusively on MySQL I would suggest checking out https://www.sequelpro.com/ - it served me well for many years.

This might be a super dumb question, but are super computers worth it? Meaning anything that requires custom hardware instead of just groups of coordinated commodity hardware. It seems you can get maaaybe 5x (10x?) current performance but at a greater (100x?) cost multiple. Or is this extra spend on custom supercomputer hardware what effectively sponsors the research that allows Moore's law to continue?

A nice one line argument for type safety.

One of the main features I look for in a language is stability. I just don't want it to change that much other than adding functionality to the standard library.

I know that's not the fashion currently, but it's probably one of the most valuable things to me.

I don't know much about this, but sure did like seeing this in the description:

"One of the main principles in Csound development is to guarantee backwards compatibility. You can still render a Csound source file from 1986 on the latest Csound release, and you should be able to render a file written today with the latest Csound in 2036."

I wish more "modern" languages and frameworks put in the effort on this point as well.

Why are you running away from it? I have occasionally toyed with using it in a couple situations, just wondering what the dealbreakers are.

This seems like a cool idea, but from reading the info on the page I don't quite understand exactly what it is. Is it a mail client? I think it is? If it is an email client, does it have mobile apps? Or do I keep using my gmail app as is?

Sorry if I'm missing the obvious, but those were my first set of questions after reading the site.

Heads up to anyone using Jetbrains IDEs, they have some great VCS history features like annotate lines: https://www.jetbrains.com/help/idea/viewing-changes-informat...

One thing to watch out for if you want to be a generalist is feelings of inadequacy. Probably because you end up knowing something about a lot of things, you are very aware that people are better than you at each of those things. It can be tough.

However, I would still heartily recommend it. It's fun! You generally are learning how to make new things, rather than new ways to make the same things.

Do you see any ARM chips on the horizon this year or next that might change the equation? It looks like Amazon is seeing 40% better performance per watt (I think they said the power draw is comparable somewhere) with their custom design, will a commercially available chip be able to match that soon?

Side note: Thanks for making a great product and keeping it cheap/free for hobby projects! I got comfortable with the basic features on a small project and now advocate for it's use regularly.

HN: I won't use anything Google makes, they always shut stuff down. Also HN: I'm all in on Go.

HN: Learn a new language every year, it's easy and worth it even the language isn't useful for anything. Also HN: I won't learn a new language that would allow me to double my mobile dev productivity because someone told me it was bad 8 years ago.

Decentralized systems generally have pretty complicated governance models and technology to support them, making it easy to get lost in the details. I've found when trying to assess things like this it's best to find a critical question and find out the details of the answer. For the case of decentralized naming, one interesting question tends to be "What happens when someone registers cocacola.com?"

Usually the answer to that question reveals whether the system is A) not in fact decentralized, or B) not compatible with laws in most jurisdictions.

Anyway, not necessarily a specific critique of this system since I don't know the answer to the question in this case. More just a useful framework I've found to assess distributed systems without getting mired in execution details.

In case you're not able to declare certain days off limits, I suggest a strategy that has worked for me in the past: schedule your work time. If you need two days to work on something, fill those two days on your calendar. It can be broken up into smaller segments (I sometimes do it in 3 hour chunks), or just the whole day. This causes an important psychological change when someone tries to book a meeting, they can see your time on the calendar and will need to ask you to make space for their meeting. This is a lot different than seeing a wide open, empty day. It forces consideration of the tradeoffs. If you work in a thoughtful company, this is usually enough to get you some space to work in a more focused way.

This is the first time I've heard Clipper mentioned in a looong time. I was just talking the other day how useful it was in those days that there were tools that included the database and UI all in one. Everything was a bit easier because the language assumed a database, rather than just using a library to interface with one.

It seems like there might be a pretty straight up tradeoff between difficulty of developing software and quantity of software produced. So the more we attempt to optimize at a lower level, the more time it takes to develop, and the less software someone can make and maintain. So, given that - would you rather lose 30-40% of the apps you use and like, but the rest are faster? Or keep using everything you have now?

There are exceptions to this, as with everything, but it's not as easy as this article makes it sound, i.e. "Just make faster stuff dummy!" There's always a cost.

The sad but true reason is because people aren't generally making rational decisions on here. They'll claim a reason, but it's usually really based on pre-conceived notions. "Google kills projects so I won't use Flutter, but will definitely go all in on GoLang" is a great example of this.

Seems like it: https://www.awea.org/wind-101/benefits-of-wind/wind-in-my-co...

Maybe a slightly biased source based on the name, but probably roughly right at least.

This sounds like the first line in a novel.

What does the performance comparison mean on this page? Does it mean a similar vCPU count A2 instance is ~40% faster than an Intel based M5 one? Or is the 40% improvement mainly through higher core count?

This hasn't been the case for most Java projects I deal with, native dependencies are fairly rare. Can't comment on Python or Node.

Seeing a Code as Craft talk at Etsy 10 years ago, or however long ago it was, changed how I develop web services completely. It was truly a revelation. Continuous deployment is fairly common now, but back then it was still radical enough that I thought "this can never work!" I never went all the way to feature flags instead of branches, but maybe I should give that a shot too.