A little display or indicator light somewhere on the toilet itself would be better than connecting it to some IOT app
A little display or indicator light somewhere on the toilet itself would be better than connecting it to some IOT app
Yeah I’d much rather spread poo particles all over my smartphone instead
Depending on how many layers of abstraction you have, your app may not have access to the raw HTTP response.
That sounds like either over-abstraction or bad abstraction then
my hard drive overheated
So, this means they either have a local copy on disk of whatever database they’re querying, or they’re dumping a remote db to disk at some point before/during/after their query, right?
Either way, I have just one question - why?
Edit: found the thread with a more in-depth explanation elsewhere in the thread: https://xcancel.com/DataRepublican/status/1900593377370087648#m
So yeah, she’s apparently toting around an external hard drive with a copy of the “multiple terabytes” large US spending database, running queries against it, then dumping the 60k-row result set to CSV for further processing.
I’m still confused at what point the external drive overheats, even if she is doing all this in a “hot humid” hotel room that she can’t run any fans I guess because her kids were asleep?
But like, all of that just adds more questions, and doesn’t really answer the first one - why?
Lmao. Sure buddy.
Try handing over your “self documenting code” to a junior dev who doesn’t know the language it’s written in and see how far they get with it.
Now hand that exact same codebase with comments to the same junior dev, and I guarantee you they’ll get further than without the comments.
It’s basically the same concept, just implemented with a k8s cluster so you have scale-to-zero capabilities I guess
And I was just adding extra details
This worry exists for literally every 3rd party dependency, not just docker, and is addressed the same way - by running tests and vulnerability scans in a sandboxed test environment before shipping to prod
Changing that kernel API wouldn’t just hurt the Rust devs, it would hurt literally anyone who uses that API, which includes other Linux maintainers. Anyone trying to “prove themselves right” by mucking with kernel APIs would swiftly be called out on their bullshit, and probably be removed from the project.
Or some kinky cubist’s wet dream
And cut into their Lemmy time? Inconceivable!
C’mon man, this is just a textbook fallacious slippery slope argument. Rust isn’t some brand new language whose stable release was less than a year ago, it’s over a decade old now. Scheme and Lisp are interpreted languages for God’s sake, it’s borderline* impossible to use them for kernel programming.
Also I’m pretty sure the whole point of the Rust project that all this drama is centered around is to keep Rust code separate from the kernel. From what I understand the whole point is to maintain Rust bindings to the kernel API as a separate project, so that if developers want to write a driver in Rust, they can without having to rewrite those bindings themselves. But the kernel code itself will still be all C code. Now I’m not a kernel developer, and the last time I wrote a driver was for my operating systems class in university over a decade ago, so take that with a grain of salt.
* I say borderline because anything is possible with code if you’re creative enough, but anyone trying to submit Scheme or Lisp code to the Linux kernel is gonna get laughed off the Internet
Plenty of UI applications* are this bad
Right? Like my dude, bare minimum at least write down those steps in a text document so you can reference it the next time you have to add something. Bonus points for putting it on some shared internal wiki or whatever Microsoft uses.
I know it’s a one-of-a-kind game, but it still amazes me that Roller Coaster Tycoon released in 1999, a game where you could have hundreds of NPCs on screen at a time, unique events and sound effects for each of those NPCs, physics simulations of roller coasters and rides, terrain manipulation, and it was all runnable on pretty basic hardware at that time. Today’s AAA games could never. I’m glad some indie games are still carrying the torch for small, efficient games that people can play on any hardware though.
This has way more to do with that specific project being poorly written/not documenting things well than any shortcomings in Python
It cant do enterprise, performance heavy, commercial stuff.
It can, I’ve been doing it for almost a decade. I’ve never noticed a lack of dev tools, and I’m not sure why .NET style project management is a prerequisite for creating enterprise applications. Obviously you can write more performant code in other languages, but I’ve found that 90% of the time, python’s performance is good enough.
Agree on picking the right tool for the job though. Most of the time though, unless you’re dealing with an extreme edge case (like writing embedded firmware for the space shuttle), that just means picking the language your team is most comfortable with.
People need to reply to those comments with “out of scope” and a link to a new issue that will get buried in the backlog more often
Yeah I find LLMs most useful to basically read the docs for me and provide it’s own sample/pseudocode. If it goes off the rails, I have to guide it back myself using natural language. Even then though it’s still just a tool that gets me going in the right direction, or helps me consider alternative solutions buried in the docs that I might have skimmed over. Rarely does it produce code that I can actually use in my project.