Of course I'd be willing to pay for new train tracks. I've wasted days of my life in northern virginia waiting for the track to free up. And they wonder why nobody uses the train!
How about a state machine encoding cart state? There are many advantages to encoding state changes in sql, but the database logic isn't strictly tied to the specifics of the cart logic. However trying to decouple these domains fully will create many more problems. There's plenty of fuzzy problems like this that interleave the technical and business.
I fail to see how ANY part of a project would fail to be of interest to a stakeholder. They don't much care whether a failure emanated from code you have labeled of interest to them or not. You certainly can't make much money without supporting the business logic with—apparently—non-business storage. Even if you can patch up the leaks in this semantic distinction between these two domains the use of such a distinction is not clear in any general sense.
These abstractions are to help the coder reason about complex systems and they don't always work. You then need to invent better abstractions.
Typically, something like this: you do something stupid like use an alternative primary key scheme (which the database is agnostic about) and then your teammate accidentally omits a parameter of the primary key, deploys to production, the query misses all the indexes and causes an incident with downtime. You don't see this problem quite as much when you're staring at the schema itself and writing code against it.
More problems: default scopes causing large refactor pain, modular queries leading to accidental joins and index misses, models containing all of the combinations of models-to-be-rows, models-that-may-be-up-to-date, and models-that-have-already-been-deleted. I prefer explicit lifecycles to avoid semantic ambiguity when it comes to what data to expect where and wehen. Generally, all the places you would expect treating database queries as code against domain objects with different semantics than database tables.
Or, my personal least favorite game, "spend three hours translating this performant query into horrendous, unreadable ruby that technically produces the sql you wanted all along". I've found this comes up repeatedly with aggregate queries and joins and window functions.
Hey ORMs have their place, but I don't get the point of pretending it's even equivalent to SQL when they were built with completely different intentions and constraints.
There's great reasons to use ORMs (rapid prototyping, for instance) but "flawless" does not inspire confidence that you are aware of the pitfalls that people experience.
Secondly, migration systems are an entirely different beast than ORMs! I'd certainly recommend that regardless.
Yea this is all interesting a language research.... but that AmdGPU.jl driver is the most interesting thing about this by a good margin. CUDA lockin sucks, sucks, sucks.
Speaking from personal experience working with these reputation warehouses and with handling a good deal of incoming and outgoing email volume, they aren't any more effective than other IP-based spam heuristics and if everyone configured their DKIM correctly these warehouses would be largely obsolete. I don't see a problem with crowdsourcing heuristic data per se, but email is a much narrower field than internet traffic at large and I can see a lot of the ways that poorly configured fail2ban type software could accidentally ban a lot of valid traffic.
There's a small chance this could (generally, not just in country) lead to online payments without going through centralized payment processors. That seems like it could be positive!
I use unsalted butter for all my cooking and use. Never grew up with salted butter and don't miss it. The vast majority of my family and friends back home (new england) use unsalted margarine (which I refuse to allow in the house).
I'm interested though, I've seen salted butter and wondered who was buying it. Now I know—literally everyone around me.
I just don't get what there is to show off. It's a phone. It's not like you built the thing! People are willing to address that these phones are "beautiful", whatever that means, without acknowledging that the differentiation mostly has class and not taste connotations.
FWIW I've used glow for a while as more or less a dumb, colorful markdown pager and had no idea this functionality was there, and I am very sure glow was not phoning home because of how I run little snitch.