His "argument" for strict typing on the Lex Fridman podcast was also that it's mostly if you have "hundreds or (of?) thousands of engineers collaborating", which "strictly" puts his opinion in the bin in my case. I have absolutely, positively become more productive as a single developer due to strict typing. Parsing various kinds of binary data was enough to convince me. A.k.a. each to their own. On the whole, Elixir and BEAM seem really cool though, and there's work being done on typing, as well as the new Gleam language.
Note: I've not yet done any serious web-development, mostly command line tools, which I realise is not DHH's main focus.
Most posts of this kind are completely void of thoughts on how society - including public institutions - require you have a smart phone nowadays.
I don't use my smart phone that much (probably more than I think, though). It's practical as a portable music/podcast player, a camera that's always with me etc. Occasionally I read a programming book, or blog post. I would love a good feature phone, with fantastic battery life.
But what I absolutely need a smart phone (and their secure enclaves) for are all the connected systems my country implements without hesitation: electronic authentication (most public services, such as healthcare, bank, taxes etc), public transport (they had seconds thoughts, though, and a plastic card is available). It's frankly dumb, and nonchalant to build societies like this. I can go into a train tunnel a lose coverage. Rural areas are not always covered, yet we (at least here) build systems depending on internet as if we all lived in the densest part of a large city.
That's primarily why I can't (currently) use a feature phone, not because I lack in self control.
At the same price level Analogue Pocket exists (https://www.analogue.co/pocket), with two fpga cores (NES, SNES, arcade cores exist), a much higher res screen (for ultimate nerdery simulating old school Game Boy screens). Besides price, I guess they're hard to get by if stock is out.
At much lower price brackets, Anbernic et al have already been mentioned. There are kits for making your own OG Game Boy as well.
Add to this that a certain P. Luckey showing up and there is not a single upside to this device...? Sorry, but I don't get it.
That's probably the reason, and has obvious sandboxing/stability benefits.
Though for iPad to be truly "Pro", there needs to be adjustments made, perhaps through entitlements or some shared storage between apps (user-chosen apps, not necessarily from the same developer as that already exists) or something similar.
You have it wrong. Apple doesn’t fundamentally believe in selling one device (do-it-all iPad Pro) as opposed to selling two (Mac + iPad). The segmentation is a business decision, nothing else.
Apple have multiple iPad lines and could easily limit a desktop class OS to the iPad Pro, a move I can almost guarantuee would alianate noone.
I don't mean to belittle your great achievement with license annoyances so forgive me if this sounds harsh, but I won't look twice at any software with an online requirement, if internet connectivity is not an integral part of the software itself. I do realise open source can be a dark, unthankful place that will not pay bills for most developers so this is not about the cost itself.
Unfortunately, pirates almost always have it easier than paying customers, since license checks will probably be removed. Though this is hearsay (anyone?), there was "legal piracy" (no, there's no such thing :P) in the license-via-printer-port-dongle-era, since the dongles sometimes failed at the worst of times (e.g. live recording at a studio). So some users/studios bought a license to be legally covered on paper, but used a pirated version.
I live in a "well-connected" country, but a traveling a few kilometers in the wrong direction leaves me in complete radio silence, and sometimes work (academia) has required me to stay at such places for a couple of days. Since you know Rust, I can (and have had the need to) add `--offline` when building, with required crates locally cached. I know many researchers with the need to bring high-tech equipment + software to remote locations for work over many weeks, sometimes months. The need to find a city just to do a software license check would be crazy.
Unfortunately, I also don't have a good solution, other than trying to trust your customers. An online check once, at install, I can possibly live with, even if I've had to do reinstalls from local files in the field as well...
He's already said the fee for you is 0. It seems he's mostly going for the university side wide licenses, I don't think issues such as yours are very important for him.
Most people at a university who want to run a computation for a few days will do it on a computer that's permanently connected to the net, I think. Not their laptop.
Regardless of our personal professional affinities the only reason iPadOS stays locked down is that it's simply more profitable to sell a customer two devices instead of just one. I would love to have an iPad Pro as my only home computer, but it's just not doable due to its OS limitations. The artistic angle is just Apple's way to make the platform believable.
Why would an artist care if I can also compile code on an iPad?
I can only assume that macOS must be offensive to some due to its "openness". The truth is that macOS allows me to be both an artist and a developer, and I don't have a single doubt that Apple could pull off an interface that allows a similar experience on iPadOS. It's just that doing so will lose them money.
> the only reason iPadOS stays locked down is that it's simply more profitable to sell a customer two devices instead of just one.
Not only do they want to sell you an iPad and a separate computer, but they would ideally like to sell your family multiple iPads, which is why you can't have more than one user account on an iPad (unless you have a business or educational account with Apple [1]).
For the brief stint I had the Vision Pro, I was so confused Apple made sharing it so hard(and it really isn’t shared - it’s just there for the free taste because it is timelimit locked). But after a little thought it clicked:
Apple only loves the idea of the VisionPro if it means you never share.
Apple has always been a walled garden, so when the iPhone imposed it nobody blinked(there are/were tradeoffs, ok). But ever since the iPod, Apple has been all about the personal device. No more multiuser anything:
- iPod
- iWatch
- iPhone
- iPad
It becomes super obvious what the “i” really stands for when you realize it was for a single person.
and now spatial computing, this new era where actual business is supposed to happen
- VisionPro
Even though the “i” isn’t there, it really should be. The power of cohesion between these devices is one of wonder. But the cohesion could still exist with standards. What we have with Apple is bad for the customer and any innovation outside apples limited interests.
I wish Britain would have went for the head and after the innovation stifling instead of the stupid port forcing. Also an innovation stifler.
Wouldn't a "month" risk being many days off the intended target date, since it's a non-fixed timespan? E.g. how many days is "1 month from today" (March 20)? You mention medicine, so I assume there's something obvious I'm missing (then again, perhaps the constantly shifting dates for health care appointments where I live say otherwise ;D).
Well, that’s not “the month” at all, though. At least not something I’d use outside of getting a rough idea for setting the next meeting, and absolutely wouldn’t use in code (but it’s probably fine for a todo - I’m complicating things, sorry ;-))
Edit: but perhaps that’s the custom used at many places and I’m just not aware.
A few people/companies I've worked with avoid using the last few days of the month for "monthly" things.
For example, "every month on the 15th", "every month on the 1st", etc. It makes it easier to figure out compared to "every 30 days" or "every month on the 30th, unless there are less than 30 days in the month"
That sounds reasonable. I'm writing a dumb, little journal/todo CLI tool for personal use ("meet with @farmer @Monday @13:30 regarding #carrots"), and the library I used for time has a duration for most things except month (i.e. you can't do 2024-03-20 + 1_MONTH), which makes sense.