you don't need to start out full blast with electric cables. ramp up over a minute if necessary. we are also well versed in circuit breakers, and digital safety checks.
oh the cable isn't correctly connected? no power.
365 karma · joined April 4, 2020
you don't need to start out full blast with electric cables. ramp up over a minute if necessary. we are also well versed in circuit breakers, and digital safety checks.
oh the cable isn't correctly connected? no power.
every piece of the system impacts this including the cable. if the cable is a bottle neck you need to fix that before any optimizations downstream can be unlocked.
this isn't 100% true. lawyers very much care about changes in legal codes over time. its incredibly time consuming to do historical legal research given how legal code changes are recorded. strike paragraph 5, insert 'foo' in section 5.3.1. etc.
there is very frequently different outcome in civil suits vs criminal suits. where you're found guilty of something in a civil court but innocent in criminal.
most things you need for a DE run as daemons.
the biggest pieces that cause problems are UI theming and application distribution. theming is less of an issue these days since applications just do their own thing anyways.
all you need for a DE is basically the wayland server, an application launcher, system tray, and settings programs.
I've been building one myself over the last couple months on top of sway (so I don't even need the wayland server). and its day to day useable for myself. two/three solid dedicated engineers can build one fairly quickly (2 - 3years).
hardest part is the UI toolkit, and there are some reasonable choices in rust. they're young but decent bases to get started.
i encounter usually 2-3 bugs (and almost always they are minor) per year due to rolling updates and usually its in the software I'm developing relying on old behaviors. and a simple package downgrade fixes it almost every time.
in theory nowadays it wouldn't be too hard to change if you use logical replication to upgrade the database but it'd be a huge undertaking for a lot of companies.
its not really surprising how you'd end up in these situations.
that being said. rate limits and error handling people. jesus. =)
I do appreciate rusts match syntax though.
it'll be fixed in about 1 year, nvidia finally got on board and built the APIs they needed to build. iirc KDE forced one of the nvidia devs to implement and then fix all the problems with nvidia on KDE wayland. basically the dev went back to nvidia and was like 'just implement the GDM apis'
only way for this to be 'incorrect' would be if someone intentionally fucked it up or disabled it.
1. the toolchain is better. (cargo ala)
2. maintenance of the software is better. (static linked binaries, easier deploys)
3. memory safety.
4. resource consumption (cpu/ram)
when I don't need 4 I use golang (most cases) because of 1, 2, and 3.
and I choose tools (all other things being equal) written in rust for the same reasons.