> To our great surprise, we've found that our codebases have a lot more declarations than assignments, so it makes sense to require the extra keyword on assignments because they're rarer.
I actually love this statistical approach to language design, draws parallels to something I read that CPU designers make optimisations to the innerworkings their instructionset based on heuristics such as average number of functions arguments etc.
This is it right here, a similar analogy this brought up was car manufacturers of old making an excuse that fatalities were the idiot drivers fault and not because of the inherent lack of safety features of the vehicle. It's too damn easy to make the wrong assumption in C & C++ and spend a painful amount of time debugging.
In my experience the added safety guarantees have made me more comfortable in "going faster" and back to vehicular terms the choice is still there to not fasten the seatbelt and go `unsafe`.
A lot, the iPad is not a computer period. It's great hardware (that has the same CPU as the MBP) with extremely limiting software, low hanging examples of limitation would be the how iPads fail to utilise any monitor properly, inability to natively open up a terminal instance and its weak filesystem. You would think given its power it would be a perfect platform to develop native applications but no, in order to get any work done you would need to remote into an actual computer which defeats the point.
Containerisation software adds so much more than just a binary with layers of indirection.
Easy fine grain control of individual application memory, namespace isolation (container to container communication on a need to know basis), A-B testing, ease of on-boarding, multi-os development, CD pipelines, ease of container restarting etc.
I echo this sentiment entirely.. mutli dev-environment, multi-machine / os things really just work. Docker et al also really shines with onboarding, the new recruit can literally get up and going in minutes.
I would not want to go back to the old ways of doing things.
From a personnel safety standpoint (what a catastrophic failure looks like in each case),
a unit installation cost standpoint (fabricate x amounts of bricks with x tolerance in the grooves plus a crane with y units of generation on top) and finally from
a complexity standpoint of stacking stacking bricks (I assume is not just going to be a stored procedure and include some kind of error correction and monitoring).
I just cant see anything positive about this solution in the slightest. I wouldn't want to be anywhere near that structure. A crane truly is a simple and well known thing but I have tangible knowledge of a large community pushback in the UK where all that was installed was a relatively small turbine on the top of a hill.
Boring and reinforcement (concrete spraying) is a tried and true technology and most importantly its out of sight.
Would a better design not to bore downwards instead of build upwards? This seems like such an over-engineered concept that could be simplified and compartmentalised drastically.
There's a whole host of negatives I see in this implementation, not to mention the downsides of erecting a crane-line structure and public opinion.
This is a UK company doing what I described above: https://gravitricity.com/ (i have no affiliation)
Another commenter echo'd this here but it's the same for me. I find running WSL2 on windows easier to get up and running and way more stable than running Linux and macOS which just 5 years ago would be the anectote of a crazy person.
Things really just work, I get a stable desktop environment, not the prettiest compared to macOS but at least the window + virtual desktop management is leagues better, and an even better development environment without dual booting.
This sounds like a cool project.
Considering its a journalling app and I'm assuming the user just enters plain text, have you experimented with compression and decompression before and after the SQLite storage?
Now go dig up the numbers of black men and women put in jail in comparison to the population. Go look up the numbers of police stops of black people in comparison to the immediate city populous. You don't have to be shot and killed for a police to ruin your life. The fact that you think people are requesting to abolish the police pretty much says it all... there is a very stark difference between redistribute high amount of tax payers money spent on police departments to arguably better community programs and efforts (defund) vs get rid of the police altogether (abolish). Think about it, internalise it, do better for your fellow man.
Currently running docker using WSL2 on an ARM laptop. So it's pretty much native Linux, as an anecdote I can tell you that it's just that much more stable than with my Mac or with a traditional Windows laptop. The only downsides is there's a few docker containers that you have to hunt around for to get the ARM64 version. The only way I see docker performance to be better than this or more stable is to switch to a Linux machine entirely.
I'll have to dig around and find relevant phoronix benchmarks later for you. But I think it's somewhat of a hive-mind assumption that Intel has generally higher performance all round. A majority of benchmarks show that Intel is generally better in single threaded benchmarks whereas ARM CPU's are better in multicore, multi-threaded applications with a lower TDP and leagues better efficiency. Heck the Surface Pro X that Microsoft brought out has performance on par with an Intel i5 with at least 1.5x the battery life of its Intel counterpart and without needing an internal fan whatsoever. I wouldn't be surprised at all if Apple will make the switch to ARM for all but their highest spec MacBook pro's.
This is exactly what I have found. I know a bunch of developers (myself included) that went from Macs to Microsoft's surface line. WSL2 has been an absolute game changer, there's something liberating about being able to launch distros of Ubuntu, Debian, Fedora etc all faster than the computer wakes up from sleep, it's literally as fast as opening the command line. Microsoft has been making big moves for developers over the past years through open source contributions, Apple literally does not care about them and this sentiment can be seen explicitly on their respective GitHub pages.
Edge Chromium and Firefox (both ARM native) is better in both speed and RAM usage, you can grab normal chrome extensions in edge Chromium too so there's literally no loss.
"fisher-price-style". Some people just want to get to work on a machine they are comfortable with rather than worrying about the looks of their machine.
Windows 10 can already run GUI apps using WSL and an X server. Microsoft is planning to build a native X server so it's frustration free. Personally, I cannot wait.
I actually love this statistical approach to language design, draws parallels to something I read that CPU designers make optimisations to the innerworkings their instructionset based on heuristics such as average number of functions arguments etc.