mtone

Except that your source of truth aka your raw data is now memoized, hardly a win. This is not a goal of memoization or dynamic programming at all.

Perfect for a reporting database though.

SSDs achieve their speed in part by combining multiple independent NAND channels under a single controller - each channel is more or less equivalent to an actuator. Their speed vary greatly based on workload parallelism, yet it's still very much one drive.

Having dual actuators (Seagate's Mach.2 branding) can increase IOPS by having 2 heads process the queue in parallel. That should bring a noticeable improvement, but it's true that it doesn't apply to sequential random (just like NCQ didn't by reordering the queue -- you need a queue).

Not sure if there will be consumer drives with this eventually or if the cost is too prohibitive.

To the last bit about promotions, I like to think that things are how we -- anyone in a team lead or manager position now or in the future -- shape them to be.

It's sad thinking about a state of affairs where I would be biased towards the person in my team I see most often - either through better guidance/collaboration (affecting promotability over time) or mere water-cooler familiarity.

For the record, I didn't say I fear nuclear. I'd pick Nuclear over coal any day. I'm not for or against any particular technology.

In normal circumstances Hydro seems among the safest [1] for both humans and the environment all things relative. It has served Quebec quite well at least with very low electricity rates and emissions, and environmental impacts are likely long paid off with no radioactive waste to manage. Being in a low populated region (a rare asset..) also helps on the safety side.

Bringing up a single dam incident due to an estimated once-in-2-millenia rainfall/typhoon [2] in a populated region to dismiss an entire renewable energy source.. sounds like that kind of irrational fear you mention.

I think the arguments around possible lack of locations, costs, planning, and water supplies are more relevant -- and affect both hydro and nuclear. Those are also what make wind/solar interesting -agility- as tech improves.

[1] https://energycentral.com/c/ec/deaths-nuclear-energy-compare...

[2] https://en.wikipedia.org/wiki/1975_Banqiao_Dam_failure#Gover...

Interesting point about water disputes, wasn't aware -- and freshwater supply is not going up in the future.

Maybe it's because I'm in Canada where several provinces use hydro as a primary energy source, but why doesn't make it to the top of the lists more often?

Nearby ecosystem damages, relatively speaking, seem rather low in comparison with nuclear or fuel, and for dealing with future climate change issues in general. While they don't explode, I'm sure they can can cause disasters of their own.

But wind/solar require massive storage capacity to become a primary source and require a lot of space/disruption at these scales. I'm not sure how the affected landmass (in the long term) compares with Hydro, or maintenance costs.

Hydro has this great combination of zero emission and the water being its own battery. Not relying on rare materials and battery production avoids adding competition and could favor the transition to electric vehicles at a global scale.

Like nuclear, initial costs are problematic. Social acceptance is so-so. In some places like the US many "good spots" are taken, but it appears 2/3 of potential in the world is untapped. More numerous but smaller damns seem to be a possibility too.

Not really - each miner (and versions of them) may have different command line arguments or monitoring APIs Nicehash wouldn't know about, so it's going to be more trouble than it's worth. I meant just starting them from the command line:

ethminer.exe -P stratum2+tcp://<your nicehash wallet address>@daggerhashimoto.usa.nicehash.com:3353

Nicehash (the app) is a convenience tool to manage miner executables -- it's mostly those that are flagged by AVs. You can connect most miner executables to Nicehash (the service) or other pools directly, and some are open-source.

For instance I GPU mine with https://github.com/ethereum-mining/ethminer and CPU mine with https://github.com/xmrig/xmrig, both built from source and I don't use Nicehash (the app). But I haven't looked at the source, so at some point I'm still trusting someone.

You now have to integrate that pattern/module, and learn/work with the tooling to integrate the pattern/module, which adds new complexity and constraints on top of the now-centralized hidden complexity.

On the whole, it’s worth it - building on the shoulders of giants lets us achieve great things with what used to require out-of-reach amount of resources.

But as a result our work has shifted towards more integration and tooling (everything from node/npm to cloud services, orchestration, containers, and ML/AI) and total complexity keeps marching on upwards.

If you ask me to draw an ampersand and a G-Clef (𝄞), I'll probably render more or less the same thing.

Possibly because in childhood I've drawn several G-Clefs but never ampersands (that I recall), while the opposite has been true later on. I suppose I've just re-purposed whatever motor memory I had for "a kind of infinite-loop G".

I see. While I don't know the details, it seems it would promote the use of "entry/barrel" files once again.

On the other hand, trying to setup a typescript monorepo with shared/dependent projects is a huge pain since everything needs to be transposed to intermediary JS that severely limits or breaks tooling.

Even TS project references make assumptions about the contents of package.json (such as the entry file), or how the compiler service for VsCode preloads types from @types/ better than for your own referenced projects, which sadly ties TS to that particular ecosystem.

Language version compatibility is a good point, but perhaps TSC could respect the compiler version and flags of each package's tsconfig.json, and ensure compatibility for minor versions of the language?

Since I enjoy working in TS I'm willing to wait it out as well, the pros far outweigh the cons. Now that GitHub/MS acquired NPM, I have hopes that it will pave the way to make TS a first-class citizen, though I don't know if Deno will be part of the solution or not.

Isn't that collusion?

Agreed I'm slightly off-topic. I was more thinking of the general thread of some things getting bigger and not always an improvement (for various reasons).

Car size have steadily increased up to the early 2010s [1] and I haven't noticed a stop to this trend, especially when including the market movements towards car-like small SUVs.

Availability of smaller cars keeps going down (Honda Fit dropped in Canada, Toyota Prius C gone, etc.)

[1]: https://www.teoalida.com/cardatabase/images/Car-Classes.png

Yes, "courriel" is the common and official [1] word in Québec. Portmanteau of courrier (mail) + électronique.

Their professional translator must have used Google Translate. But much worse translations are common in our corner of North America.

"Work" is the tricky part. I generally use e-mail (work) rather than trying to translate verbatim as it tends to read like "E-mail at the office" or "Professional e-mail", both weird.

[1] http://www.gdt.oqlf.gouv.qc.ca/ficheOqlf.aspx?Id_Fiche=83539...

I run a little powershell script on build that adds the [System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverage] attribute to generated classes in certain folders.

https://gist.github.com/mtone/aded2ff636cb6dd9d428cf5800f344...

Funnily, I have no clue how to setup a build script in Rider, did that in VS (Rider do run it).

| one would need to download everything

Just download it then. We got mp3 albums off Napster on modems back in the day, surely getting that torrent is easier and faster today.

One thing no browsers I'm aware of does right is re-highlighting matches after clicking a link. Firefox keeps the search bar open, but you still need to re-trigger it to update the match count and highlight. Chrome just closes it, sigh, although that is a more accurate UI for the behavior.

Indeed, but I also count that as a support ticket!

Also happy with my move to Firefox, it surpassed my expectations. Two (small) pain points have been:

- customizing userChrome.css .. It was a bit time consuming to figure out first (I wanted to remove the top bar and use vertical tabs). Happy to be able to do it, but it's not exactly user-friendly.

- Rejection of Windows local certificates store that requires fiddling with a setting to enable. If my certificate store is compromised Firefox is not going to save me. I don't recommend it over Chrome at work since we have one of these for a local server and I'd rather not generate support tickets.

Both of these are not part of Firefox Sync and require manual handling on each PC.

Another potential area might be unit testing. As an example, I've been running a test suite on a C# github project (xUnit and mocking libraries) with ~1.5K tests. The CPU is at a solid 100% cpu usage all the way through.

In higher-level languages, running tests often takes considerably more time than building. A prosumer CPU like this would bring nice day to day improvements.

The source code is in .ts, and appears to use Node child processes [0], so probably yes. I'd be curious to see the kind of resource usage is involved building TSC.

My limited experience using Node worker threads (to compile small React apps with WebPack in parallel) showed lots of overhead and memory usage for just starting the build (Node and library instances, can't say in what proportion), although it is still worth the expense.

[0] https://github.com/microsoft/TypeScript/blob/master/scripts/...

Of course they've been going up, but per capita they might reach equilibrium before NA levels.

Europe is doing quite well on that chart.

[0] https://www.google.com/publicdata/explore?ds=d5bncppjof8f9_&...

If recent history is any indication, I don't believe that walled garden software will make for repairable, longer lasting, customizable cars rather than being used for planned obsolescence.

> if you're interested in any particular paragraph, you can click and see a whole discussion on "just that paragraph"

Only if you're subscribed.

Using Acrobat DC, searching for content in all PDFs in a folder takes ages. It is both slow AND single-threaded, the disk is barely moving.

Tried with Foxit and a few others, same thing. I had to seek indexed search apps, and those are few and far between and generally poor quality - kudos to Recoll[1] as the standout so far. But I'd much rather just search within the reader.

Anyway, it's infuriating, this should go about x times as fast as there are cores.

[1]: https://www.lesbonscomptes.com/recoll/

https://www.anandtech.com (Ian Cutress et al.) has good regular "deep dive" pieces. David Kanter at https://www.realworldtech.com is worth a read, although his site is not as active.

Ultrawidify on Firefox is doing a pretty good job at stretching it out to 21:9 (dynamically so it switches on the xBox logo part).