Modern machines are so insanely fast, the UI should almost react before you do an action.
My 5900X machine with relatively slow RAM running CachyOS actually almost feels as instant as DOS machines with incredible low latency.
Instead, we get tons of layers of abstraction (Electron etc), combined with endpoint security software in the enterprise world that bring any machine to its knees by inspecting every I/O action.
Zed is an awesome editor where every interaction is just “snappy”.
I feel all the animations and transitions have been introduced to macOS just to paper over slowness. I’ve disabled them via the accessibility settings which helps in perceived snappiness a bit, but it also makes yank visible where performance is not up to par.
That it actually quite simple and nifty. It reminds me of the 4 priorities RPC requests can have within the Google stack. 0 being if this fails it will result in a big fat error for the user to 3, we don’t care if this fails because we will run the analysis job again in a month or so.
IIRC in macOS you do need to pass the voucher, it isn’t inherited automatically. Linux has no knowledge of it, so first it has to be introduced as a concept and then apps have to start using it.
It can boot and show a desktop fast after logging in. However, after that it seems still to be doing a lot in the background. If I try to open up Firefox, or any other app, immediately after I see the desktop it will take forever to load. When I let the desktop sit for a minute and then open Firefox it opens instantly.
Presumably a whole bunch of services are still being (lazy?) loaded.
On the other hand, my cachyos install takes a bit longer to boot, but after it jumps to the desktop all apps that are autostart just jump into view instantly.
Most time on boot seems to be spent on initializing drives and finding the right boot drive and load it.
IIRC everything you compile on macOS yourself, possibly only when using Apple’s llvm toolchain, already gets the proper bits set to execute just fine. This also seems to work for rust and go binaries. I’m not sure whether that is because they replicated the macOS llvm toolchain behaviour for the flag or whether another mechanism is at play.
Apple has this thing called Legacy Contact which allows the same but then built in to the whole Apple account. This includes devices as well as the iCloud ~~and attached keychains. Granted, it is another hoop to jump through compared to presharing keys with each other.~~
It would be nice if your Apple account could be unlocked with some other keys as well apart from the primary one, but I guess that is what Apple calls the “Legacy Contact Key”.
Edit: okay so the keychain is excluded from this. So back to storing each others passwords in eachothers keychain…
You can though. GHA and Gitlab CI and all the others have a large feature set for orchestration (build matrices, triggers,etc.) that are hard to test on a local setup. Sometimes they interfere with the build because of flags, or the build fails because it got orchestrated on a different machine, or a package is missing, or the cache key was misconfigured, etc.
There are a bunch of failures of a build that have nothing to do with how your build itself works. Asking teams to rebuild all that orchestration logic into their builds is madness. We shouldn’t ask teams to have to replicate tests for features that are in the CI they use.
Indeed there are. But you iterate on local and care about CI once everything is working in local. It's not every tuesday I get CI errors because a package was missing. It's rare unless you're in those 1000-little-microservice shops.
It is rare for our run of the mill Java apps to however, we notice it with:
Integration of code quality gates, documentation checks, linting, cross architecture builds, etc.
Most of this can be solved by doing the builds in a docker image that we also maintain ourselves. Then what remains is the interaction between the ci config for matrices, the tasks/actions to report back quality metrics, the integration with keyvaults to obtain deploy time secrets, etc.
Then there are the soft failures, missing a cache key causing many packages to be downloaded over and over again, or the same for the docker base images, etc.
We fix this for our 1000+ microservices, across hundreds of teams by maintaining a template that all services are mandated to use. It removes whole classes of errors and introduces whatever shenanigans we introduce. But it works for us.
If GHA, Azure Pipelines, etc., would provide a way of running builds locally that would speed up our development greatly.
Until then we have created linting based on CUE to parse the various yamls, resolving references to keystores, key ids, templates, etc., and making sure they exist. I think this is generic enough to open source even.
I still think MS Access was awesome. In the small companies I worked it was used successfully by moderately tech savvy directors and support employees to manage ERP, license generation, invoices, etc.
The most heard gripe was the concurrent access to the database file but I think that was solved by backing the forms by accessing anything over odbc.
It looked terrible but also was highly functional.
Agreed! The first piece of software I built was a simple inventory and sales management system, around 2000. I was 16 and it was just about my first experience programming.
It was for school, and I recently found the write up and was surprised how well the system worked.
Ever since I've marvelled at how easy it was to build something highly functional that could incorporate complex business logic, and wished there was a more modern equivalent.
Grist[1] is great for this stuff, at first glance its a spreadsheet but that spreadsheet is backed by a SQLite database and you can put an actual UI on top of it without leaving the tool, or you can write full blown plugins in Javascript and HTML if you need to go further than that.
Just another yay for Grist here! I've been looking for an Access alternative for quite a while and nothing really comes close. You can try hacking it together with various BI tools, but nothing really feels as accessible as the original Access. While it's not a 1:1 mapping and the graphical report building is not really there, you can still achieve what you need. It's like Access 2.0 to me.
Access as a front end for mssqlserver ran great in a small shop. Seems like there was a wizard that imported the the access tables easily into sqlserver.
I've not seen anything as easy to use as the Access visual query builder and drag-n-drop report builder thing.
This is amazing! My wife is also planning to open up a bakery and I was thinking of building something similar. Hadn’t thought of that daily production workflow, just the ingredients and recipes into cost/labour/profit parts.
Some small things:
When trying to edit a product (almond cookies) on the phone, I cannot scroll the pop-up so cannot go to all fields or the save button.
When calculating the total calories it prints kg as the unit instead of cal.
On the overview page of materials for a product it only shows “grams” per ingredient without the actual number.
Which models are you looking at? I was still quoted separate pumps for floor heating and a boiler with the pump built in taking the energy from the air two years ago.
> The South Korean giant [Samsung] said its new EHS All-in-One provides air heating and cooling, floor heating, and hot water from a single outdoor unit. It can supply hot water up to 65 C in below-zero weather.
> Dubbed EHS All-in-One, the system provides air heating and cooling, floor heating, and hot water from a single outdoor unit. It is initially released for the European market, with a Korean rollout expected within a year. “It delivers stable performance across diverse weather conditions. It can supply hot water up to 65 C even in below-zero weather and is designed to operate heating even in severe cold down to -25 C,” the company said in a statement. “The system also uses the R32 refrigerant, which has a substantially lower impact on global warming compared with the older R410A refrigerant.”
reply