robertjpayne

This is oversimplifying. The path to a good career after graduation is still fraught with many traps and pitfalls.

Ask anyone who finished university in late 2008 to 2010 how their job prospects were compared to those that finished just two years earlier in 2006.

Compounded by the fact that there is no way to discharge the debt if you get exploited into signing up to $100,000+ of debt for a degree that provides no good stable income afterwards.

Make no mistake most humans will exploit any glitches and bugs they can find for personal advantage in game. It’s just machines can exploit timing bugs better.

To their credit Xcode ships with all these things built in and you don’t have to make decisions about what to use.

Yes it’s not as good as some other technologies but for Things use case and sorts it’s a good match.

And the predictive code completion is pretty bare bones awful compared to what you get in VSCode/Cursor or other editors.

Ruby really isn't that slow -- even so most of its "performance" problems are due to idling waiting for I/O not actual code.

If you care about power consumption of computing you need to be looking at current AI and crypto currencies consumption like Bitcoin…

Personally don't feel like it's going to shift much.

For devs who make a living off hosting/plugins/themes they might keep an eye on things but why move if the money is still coming in?

For users, I doubt much of them will ever know or care -- unless you're on WP engine.

Wordpress is still the most widely available, cheapest and easiest (for non-tech user) to customise software to make a website with.

I reckon they will change the license terms much like Facebook licenses llama.

What?!? You argue disadvantaged shouldn’t be taxed but argue they should be on the hook for their own healthcare? Insanity.

JavaScriptCore doesn't use a JIT when used in your own apps. When you embed a WKWebView it runs out-of-process and has JIT enabled. Without the entitlement you cannot execute any written memory by your own process.

All 3rd party browsers today use WKWebView and add their own "chrome" over the rendered page. In essence Chrome/Firefox for iOS are really just Safari with custom chrome for bookmarks etc…

You can implement the same syntax for a renderer on other platforms but all of SwiftUI is closed source. So the diffing engine etc… all would need to be re-created from the ground up.

SwiftUI, like react uses some language constructs to make it look really fancy but in reality it's really simple nested data structs.

The real hard part is what the "DOM" provides for React and likewise what UIKit/iOS is doing with those data structs.

He uses cost in a context of time and effort not directly financial

I absolutely love the idea of both sides being able to "try before you buy". Some jobs just suck for the employee and they wont know until they're a month or so in and it's a waste of effort for both parties to continue cordially expecting it to magically get better.

And we should strive to reduce a world where car ownership is a thing. The world would be a much better place if we didn't eat up so much damn space/resources/economic output for personal cars.

If you value your life you won't let a Tesla ever drive you without paying attention the entire time.

This is the myth that everyone is going to be screwed by. Nobody is going to be legally responsible for malware that ends up on your device.

The only difference is Apple has the $$ and incentives to remove it as soon as it's brought to their attention (assuming it's actual malware that may cause large financial loss not just copyright infringement).

Alt-stores will be ridden with malware and nobody is going to be legally responsible for it. We can just hope the alt-stores that end up existing have incentives to keep them "clean".

Not necessarily true. Sometimes new prescriptions can take some time to adjust to if it's been a long time since the last prescription. Once you settle in they are 100% rock solid but it can be a few days of weirdness as your eyes adjust.

The biggest thing is that your eyes will naturally "strengthen" to make up for loss of acuity with an old prescription and a new prescription will correct that immediately and thus you end up with a mismatch that takes awhile to settle.

You're basically asking the EU to compel Apple to open up their platform and all their R&D that goes into their toolchains to developers for free at no charge.

This is rapidly changing with Tesla first. Outside the tires not much you're going to get after-market except from Tesla.

You always have the option to not buy a ford, or not buy an iPhone.

This gets brought up every time someone talks about macOS and MacBooks.

Another thing people don’t take into account is the time and thus money saved not dealing with this crap.

Building PCs from raw parts is annoying for heaps of people. Warranties are annoying, making sure all the parts fit together is annoying. You’ll spend the extra cost in short order just making sure you have the right parts.

Also resell value of MacBooks is very very good. When it’s time to upgrade you typically are losing 20-30% of purchase price at around the 2-3 year mark. Where as PCs are hard to give away at times.

Everyone has their own needs but Apples machines for me are a work tool, I need a laptop and nobody comes even close to the quality or peeper dollar spent in the form factor.

They do in the sense that socialised medicine wont cover all treatments. In New Zealand some things are not "funded" but you can still get private cover to extend to cover state of the art treatments and be able to skip the queue.

The difference is, that insurance costs a fraction of what it costs in the USA because the basics are all covered and the cost of providing state of the art care is drastically reduced since the hospital facilities/bed are still covered publicly.

> If you're new here, I'm Lee. I work on Next.js. I've also made some courses about using Next.js before I joined Vercel.

This alone should be further up the post…

This 100%, we're not done with batteries yet as a society and it's probably one of the most heavily funded industries because the opportunity to strike "gold" with good battery tech is too large to ignore.

Lithium wont be used forever and and downsides to batteries will slowly be eroded until we wonder why we ever used petrol in the first place.

As far as the grid goes, in my eyes rooftop solar is going to provide a huge amount of the power generation required for EVs. We're not there yet but the price of solar keeps dropping rapidly and you'll see a shift in messaging from "discounts and charge overnight when demand is low" to "discounts and charge during the day because generation is high".

Fuel definitely goes bad, at least once the storage is in vehicles. The petroleum industry keeps peddling all this FUD about how awful batteries are.

The difference is batteries can be improved (and there's a tooooon of $$$$ pouring into this problem) and they are improving. Petroleum is a dead end while batteries, solar, and electrical grids have a bright future and lost of room for growth.

What parts of Bun were you using? All the features I've used (that work*) are faster, the hard part is the compatibility is still lacking so turning on the Bun runtime over just using Node is tricky.

Benchmarks like this are misleading. Unless you're already webscale you wont need to manage this level of concurrency at high throughput.

Instead focus on tech decisions that enable you to ship what your paying customers want faster be it PHP, JavaScript, Node, Bun, Go…

I really doubt this. Messing with high voltage battery packs will get people killed very fast. It's not an inert part with barely any risks.

That doesn't take into the account the software required to safely and properly charge these packs that will likely be factory or dealership locked to a vehicle if thefts start to happen on a larger scale.

Kotlin running on the JVM is a disadvantage outside of Android though in a lot of spaces. Rust/Swift/Go will use a fraction of the ram to run a server application than Kotlin will.

The fees don't kick in until you get to a certain number of lifetime installs. Once you start paying the install fees the price per install drops quite rapidly too.

The fees are also PER-GAME so one popular game wont cause your new game to cost a bunch immediately.

It sounds way less bad than what people are making out to be (still not free, but should anything be?)

I'd actually love to be proven wrong, Couchbase looks awesome on paper but some Couchbase staff even confirmed this with me here https://forums.couchbase.com/t/persistence-durability-guaren...

Couchbase is a very very different product under the hood. Be aware you have to run Couchbase with their minimum spec cluster requirements ( 3 nodes, tons of CPU and RAM ) just to ensure you don't lose data because it syncs from ram to disk at best every 100ms