bauta-steen

Sounds interesting, can you give an example on how you (or your) agents work with fossil. How do (you make) the agents "think" inside (the repo)?

Truck (Rust CAD Kernel) - https://github.com/ricosjp/truck

To get started with Fenics you can maybe use the FEATool GUI, which makes it easier to set up FEA models, and also export Python simulation scripts to learn or modify the Fenics syntax [1].

[1]: https://www.featool.com/tutorial/2017/06/16/Python-Multiphys...

And interestingly "the oldest known public version-controlled codebase in the world that's still under active development" dating back to 1979.

[1] https://en.wikipedia.org/wiki/BRL-CAD#toc-History

Not OP either, for me due to RSI I've switched to use a touchscreen when I can, and alternate the mouse between left/right when I have to use one (Ergo mouse and similar never seemed to do anything for me). As well as a super light/smooth keyswitch keyboard (Fujitsu Libertouch with cut domes).

When you mention:

> 3. No mechanically clicking keyboards and mice. That's is a nerve hit 1000s right there times a day.

I'm curious how do you go about replacing the keyboard? You can replace the mouse with touchpads, touchscreens, trackballs etc. but what is you effective keyboard replacement (speech to text maybe)? Or do you mean no clicky-switches (for example Cherry blue)?

I think they missed a bit by upping the total weight to ~4.2 lbs, and not making the keyboard "sandwichable" like Gen 1 (so you can just open it in clamshell mode directly, they keyboard now seems to attach on the outside via a bulky stand).

BTW Gen 1 seems to currently be on sale (on Amazon) for ~1100 USD in the US.

I've had trigger finger in my pinkies for maybe 10 years now.

To my knowledge nothing except for maybe surgery will cure it. Excessive typing will unsurprisingly exacerbate it. I manage by remapping keys from the pinkies (emacs + ahk + Japanese keyboard with thumb keys), and using a keyboard with ultra light switches (Fujitsu libertouch with light membranes, plus cut slits in them to make them even lighter).

emacs

Just 'spy' used to return one of the "spy vs spy" guys, but now seems to result in a dog.

Perhaps the main issue is that even if a PDE solver supports distributed CPU parallelism, the distributed block solvers do not typically allow for decoupling to thousands of independent threads that GPUs are good at. Therefore as the PDE problems and solvers are tightly coupled they do not easily parallelize to GPUs and don't allow for simple recompilation with GPU targets. Most often an existing code would require a complete rewrite/redesign (man years of work for big code bases), at least if there are to be any gains to be had. There are new codes coming, particularly in academia, utilizing GPUs. From what I've seen one can expect around 10x improvement switching to GPUs, so it's good, but not magnitudes better considering the work involved.

Actually,what does an emacs server running in wsl get you rather than just running the standard win32 build?

Isn't the emacs core (excluding packages) known to be very stable? At least I've only had one crash in a year or so, most likely due to some package misbehaving.

Very interesting, just tested on 0.5 and vectorized can still be a magnitude slower.

ulia> @time vect(x, y, a, b) 0.000038 seconds (29 allocations: 37.406 KB) 1×2 Array{Float64,2}:

julia> @time devect(x, y, a, b) 0.000006 seconds (10 allocations: 512 bytes) 1×2 Array{Float64,2}:

julia> @time vect(x, y, a, b) 0.002324 seconds (73 allocations: 3.075 MB) 416×2 Array{Float64,2}:

julia> @time devect(x, y, a, b) 0.000206 seconds (18 allocations: 23.359 KB) 416×2 Array{Float64,2}: