phartenfeller

The medical machine software should just refuse to run with an error message if a critical driver was not loaded. The OS bricking is causing way more trouble where an IT technician now needs to fix something where it otherwise would just be updating the faulty driver... Also does your car not start if you are missing water for the wiper?

Nope, for me it includes the Android version but no device model information.

Thanks for the feedback. Didn't know this was the case. I created an issue and will implement this the next time I find time :)

Oh, this is the origin of the recent HN traffic. Thanks for the shoutout! I started this six years ago during boring university lectures to get better at Web dev. Now I get on average 50 users per month; it's nice to see when others enjoy it.

No as the page's URL is still not the real login URL. The shown address bar is just a fake with styled website content if I understood it correctly. Really smart!

Huge oligopolistic algorithms tend to homogenize consumer behavior, so I think it's not wrong to support local and small artists. Additionally, giants can even influence the algorithms to favor their new hits [0]. I am also not sure how much tax avoidance is happening in Canada.

[0]: https://www.theverge.com/2020/11/2/21545958/spotify-artist-t...

Yes, the 30% is too much; they should take less, especially for indie developers and small studios.

Nonetheless, are Valve, Steam and SteamDeck the only reasons I spend money on games. Where other publishers just provide a storefront for their own games, Steam builds a customer-pleasing platform where, unlike Apple, you have the choice to go to another store. Additionally, their recommendation systems encourage people to buy niche/indie games and not only the most expensive AAA titles.

I hope Gabe Newell stays strong and keeps to his fundamentals. I guess all contributions to making gaming easier on Linux would have not happened under a publicly traded company.

For me the interesting part is that the crawler is going bezerk. Never ever should a single crawler be the cause of 80% of traffic.

Also why should they not respect the 403? Crawlers just go to anything they can find. It is not a targeted attack.

I want a feature to save a tracker as unharmful. Friends of mine carry AirTags on their keys, and if I go for a walk with them, I get the tracker alert every time.

Just looking at the database release (not the company behind it), I think this is a great release. JSON Duality Views [1] are a phenomenal feature to bridge the gap between relational and document data without having any downsides. In the same fashion, Property Graphs [2] allow traversing relational data in graph fashion.

With these and the new vector features, their multimodel approach is paying off, in my opinion. Their JSON storage format (OSON [3]) is also very fast and efficient.

[1] https://oracle-base.com/articles/23c/json-relational-duality... [2] https://oracle-base.com/articles/23c/sql-property-graphs-and... [3] https://blogs.oracle.com/database/post/autonomous-json-datab...

As a database person, I think most ORMs lack the ability to run complex queries. Sure, for a simple OLTP system, you might just need a few simple joins. But if you store valuable data (otherwise why store it), you will eventually want to ask questions about it.

So this ORM positively surprised me, as you can still just use SQL and get a JS function generated from it.

To bridge object-to-relational mapping, Oracle has an interesting concept called "JSON duality views". Don't dismiss it because it is Oracle, I think the concept is brilliant. The translation from relational to JSON happens in the database, and it also allows you to send an updated JSON back and the DB will automatically run the necessary DML operations. A good example is here: https://oracle-base.com/articles/23c/json-relational-duality...

You can store SQL queries in views that you can version in Git. In "enterprise" databases like Postgres, Oracle and MSSQL, you can also store statements in procedures/functions that you can also store in Git. We also do Git based migration scripts that create new / update existing views, tables, procedures, data, etc. This happens automatically on test servers and can be rolled out to production.

It is somewhat tricky to build such an infrastructure and differs from "traditional" backend software, but it is what it is with Databases that heavily rely on state. The benefit is that you save a lot of bandwidth when you process the data on the machine where they live, and the architecture of the IT landscape is way simpler.

Kind of unsurprising that steel on steel transfers energy better into forward momentum. I am curious how the footprint is for subways in big cities. Full trains, cost efficiency and ease of use should be way better there.

Do you expect a perfectly built out rail system to just spawn? No of course you need to start somewhere and articles like these are one argument to do so.

Interesting idea but I think one huge factor for cosmetics in games is status. Other people see, what cosmetics you have and this encourages people to show off expensive stuff. This does not apply to a personal UI.

And what about people judging the app on the first look? Good design can interest people in checking out what the site is actually about in the first place.

I think removing persistent storage and the ability to add websites to the home screen makes it obvious what their strategy is. The EU shows that they want interoperability for big players like they do with messenger interoperability in the DMA. The web is such a fundamental standard and its interoperability is so important I guess the EU will fine Apple for such behavior. The question is how soon this will happen.

I fully agree, and that is precisely why the EU is doing a great job regulating this, and they shouldn't stop and punish Apple more for their response actions.

Apple should allow other browser engines, and these should be able to leverage the OS capabilities comparable OSes are giving to their browsers.

I agree that native apps can offer better experiences and often do because they get more development effort. I disagree that most people hate PWAs because they are just websites.

I think many mix bad websites with "PWA is a bad technology". All the cookie banners, ads and prompts to install the native app are the reason the experience is worse.

What could a native app for Wikipedia, Google or a basic news pages (without ads) do better? I use the Twitter PWA for years as it saves battery and offers the same experience. Maybe animations are not as smooth but most people won't even notice that. I also rather use YouTube in Firefox mobile so I can use uBlock even though the app offers more features and generally more ambition. For hardware heavy use cases native apps are obviously better.

Also when companies push people to install the native apps for quick access, push notifications and better data collection you can't take customer usage as a metric for people's taste.

I work with Oracle daily and implement a lot of logic directly in the database.

Debugging: Extensive logging to tables [0]. Also we have dev, test and prod databases.

Versioning: Git. It's just source code that gets compiled in the db.

Deployment: Upgrade SQL scripts. You already have to do this on any relational DB if you need to alter existing tables. We just also deploy new/updated packages. We trigger them via pipelines.

Also keep in mind that the logic you deploy in the database is generally not as complex as other software as you mostly just query, modify and write highly structured data.

But we still run plenty of tests. There is a great unit testing tool for Oracle: utPLSQL [1]. We also spin up databases and run the installation and upgrade scripts on pull-requests.

[0] https://github.com/OraOpenSource/Logger [1] https://github.com/utPLSQL/utPLSQL

Why not debate what they say? Whoever brings up an argument doesn't matter if they have a point, in my opinion. Otherwise it would be ad hominem: https://en.m.wikipedia.org/wiki/Ad_hominem .

I have been working as a database consultant for a few years. I am, of course, in my bubble, but there are a few things I really don't enjoy reading.

> No single data model can support all use cases. This is a major reason why so many different databases exist with differing data models. So it’s common for companies to use multiple databases in order to handle their varying use cases.

I hate that this is a common way of communicating this nowadays. Relational has been the mother of all data models for decades. In my opinion, you need a good reason to use something different. And this is also not an XOR. In the relational world, you can do K/V tables, store and query documents, and use graph functions for some DBs. And relational has so many safety tools to enforce data quality (e.g. ref. integrity, constraints, transactions, and unique keys). Data quality is always important in the long run.

> Every programmer using relational databases eventually runs into the normalization versus denormalization problem. [...] Oftentimes, that extra work is so much you’re forced to denormalize the database to improve performance.

I was never forced to denormalize something. Almost always, poor SQL queries are a problem. I guess this can be true for web hyperscalers, but these are exceptions.

I'm wondering why there isn't a calendar API available. I wanted to create a simple PWA to track upcoming events for my favorite sports. It would be convenient to sync these events with my phone's calendar. Currently, downloading .ical files isn't a sufficient solution because it requires accepting prompts for each event and doesn't allow for modifications (as I am aware).

Same logic as why you need worker/renter rights, just find another employer/apartment. Sorry that the toaster shocked your wife, but you could have just gotten a different one with better safety standards.

It is great that the government protects consumers. Otherwise, everyone would need to spend hours researching everything before making a rare purchase.

"The team removed table joins and complex queries from the database layer."

As a database person, I dislike reading this. I understand their need and priority to keep things running. But I would have loved it if they emphasized that doing something like this has so many disadvantages.

Normalization, referential integrity and a powerful query language bring so many benefits. I see young people oftentimes seeing relational vs. NoSQL as two totally valid opinions, like Coke vs. Pepsi. And not as one thing runs the world for decades and is perfect for >90% of use cases, and the other one is for niche cases and fast hyper-scalers.

> The quality of web software is underwhelming

I hate where "web scale" has brought us. Because some 0.01% of giants have tremendous scalability problems, every small project needs an overly complicated architecture that consists of layers of services. In the end, nobody understands the monster, and the complexity brings more issues than it solves. But still, this is somehow a standard today.

I have a lot of love for static HTML sites or simple backend/frontend solutions. The web is great, but current development trends are not.

Interestingly, the processors changed slightly. Slightly smaller dies and GPU efficiency cores. But it seems like there are no real performance gains.

OLED version: 6 nm AMD APU CPU: Zen 2 4c/8t, 2.4-3.5GHz (up to 448 GFlops FP32) GPU: 8 RDNA 2 CUs, 1.6GHz (1.6 TFlops FP32) APU power: 4-15W

LCD (old) version: 7 nm AMD APU CPU: Zen 2 4c/8t, 2.4-3.5GHz (up to 448 GFlops FP32) GPU: 8 RDNA 2 CUs, 1.0-1.6GHz (up to 1.6 TFlops FP32) APU power: 4-15W

SvelteKit + SQLite for me. SvelteKit is easy to pick up and their standards make sense to me.

Of course SQLite has limits but it takes a lot of complexity or concurrent users to come close to them.

Great! C3 is always something to look forward to between Christmas and the new year.

Electron has always had capabilities that websites don't have. VS Code, e.g., has shell integration, uses file watchers, lets you connect to remote servers or your container runtime, interacts with other installed programs, etc. I don't want to miss these features, which is why I don't want to use the web version.