skysight-inc/HackerNews huggingface dataset:
Mighty is such a great example of attacking the symptom(s) of the problem ("Chrome/the web is slow") rather than the root cause (rampant page size/complexity bloat, inefficient use of RAM/CPU, etc.). What a waste of talent and money.
Sure: "A pollutant or novel entity is a substance or energy introduced into the environment that has undesired effects, or adversely affects the usefulness of a resource." From Wikipedia.

A "novel entity" i.e. anything that doesn't belong in the air. Wikipedia adds that it must in some way harm things to be a pollutant, which is a reasonable addition.
This is actually good advice for building most software products.
Do you really save energy by recycling paper?
Rich Hickey talks about this, calling it "hammock-driven development."

https://www.youtube.com/watch?v=f84n5oFoZBc

Aaron Sorkin has also touched on this:

> Most of the time, me writing looks—to the untrained eye—like someone watching ESPN. The truth is if you did a pie chart of the writing process, most of the time is spent thinking. When you’re loaded up and ready to go—when you’ve got that intention and obstacle for the first scene that’s all you need. For me at least, getting started is 90% of the battle. The difference between page zero and page two is all the difference in the world.
Sad to see this is the lowest-voted comment here while simultaneously people above in the thread are replying with things like "I'm not sure how I'd provision servers without something like Docker" thereby proving your point.

The vast majority of comments have nothing to do with containerization which is the purpose of Docker and unfortunately Docker just isn't that great at it. Meanwhile, they use it for configuration and in lieu of system administration which has multiple drawbacks and does indeed waste resources.

I'm sure I'll be downvoted as well but thought I'd comment so you don't feel so alone. Keep doing things the right way.
> Is there some other expensive thing the grid tie is doing

Legal permits and network regulations are the expense I would guess. Probably nothing particularly technically difficult.
The Hans Nieman Case Numbers
Sailing downwind faster than the wind is possible. "Apparent wind sailing"
https://en.m.wikipedia.org/wiki/High-performance_sailing

Even more astonishingly are the remote controlled sail planes than not only exceed the speed of the wind, their performance is limited by the sound barrier. "Dynamic soaring"
https://newatlas.com/aircraft/dynamic-soaring-speed-record-s...
An excellent example of cutting the Gordian Knot: https://en.wikipedia.org/wiki/Gordian_Knot
I think you're confusing some things. First of all, "just uploading" the binary only works in languages with a very lazy approach to modularization, aka static linking. But thinking that uploading binaries "works" is a fallacy in itself. Just look at the binaries you're producing, they probably have at least a couple of dynamically linked dependencies.

Second, interpreted languages could work in exactly the same way. I am not sure, but I think there are tools in Javascript land that gobble all dependencies together into one script. But even with python or lisp, you could easily copy the whole folder (venv in Python lingo) around. If you need to, just add an interpreter as well.

Finally, even Docker doesn't guarantee you perfect portability. Every application you code also has an implicit dependency on the kernel ABI. It's just that Linus et. al. do a really good job at avoiding ABI breakage. That's why you so often succeed in copying binary code around.
Companies have a need to randomly change designs so that the new version looks different and people understand "it's new".
We don't even need to speculate about it. In for example Sweden, everyone's tax return is public information. You just call the tax office and ask how much income someone declared last available year.
Generating chess puzzles with generic algorithms (2022)
So the study does not account/adjust for other factors.

Very interesting.
There's a lot of talk about Niklas Luhmann's method of zettelkasten, but what about the 500 years of the related practice that was also highly productive?
(I'm using MVP.css for my homepage)

Shouldn't have HTML a decent look out of the box?
My 2013 MacBook Pro is/was my last Mac. It worked just fine, but I opted out of newer OS X updates because I noticed each successive "upgrade" was making the OS worse, in countless ways, and adding exactly zero improvement I could discern. Change for the sake of change, as far as I'm concerned. I feel the same way about Windows...

I ended up just going out and buying a bunch of old ThinkPads and running OpenBSD and Linux on them. I think I got like five computers for less than the price of a single MacBook Air.

I'm pretty much done with proprietary operating systems because they clearly no longer provide the best experience, from my perspective.

I'm tired of being locked out of software I paid for because I "upgraded" the OS (looking at you, Logic Pro), or vice versa, unable to use new software because I didn't "upgrade" (most new Mac software won't run on my MBP). If I upgrade, I literally throw away a $250 piece of software and have to spend another $250 (or whatever) to use the new version of _that same software_. At least open-source OSes allow me to stay up to date while still having nearly-maximum agency over how the computer works and what software it runs.

I'm tired of my computer doing a ton of stuff I didn't tell it to do. The amount of notifications/nags/etc. on a modern Mac/Windows computer is absolutely mind-boggling to me. The always-online aspect, software-update-checks, "telemetry" and "analytics", phoning home every time I launch a program...

I'm tired of my computer not being a tool for me to use, but rather just a gateway to a bunch of stores and ways I can spend money, with a bit of "productivity" sprinkled on the side. I could go on and on.

Oh, I didn't even touch on the software design/UX aspects. Like Riccardo wrote, it's a worthy of an entire article itself. I could probably spend an entire day documenting/critiquing the degradation of user experience in Mac OS and Windows. Mac OS had a lot further to fall, and indeed has been extra-disappointing because I used to hold it in such high regard :\
In Spain now the best pigs (for eating) are fed foraging on acorns.
You should have gone to VCs. Maybe could've raised some capital. Could've been huge!
Yeah, it's socially fit, so a big chunk of the crowd naturally converged on it because it reduced efforts enough.
you talk about cholesterol? My grandma got it.
The academic analogue would be: Programming in Haskell, by Graham Hutton http://www.cs.nott.ac.uk/~pszgmh/pih.html
> BetterTouchTool

Physical function keys are a must-have for every mac imo
Well sir, this was a matter of pride!
Chesterton's Fence:

There exists in such a case a certain institution or law; let us say, for the sake of simplicity, a fence or gate erected across a road. The more modern type of reformer goes gaily up to it and says, “I don’t see the use of this; let us clear it away.” To which the more intelligent type of reformer will do well to answer: “If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.”
Pycharm still struggles to provide debug of Python interpreters running in local docker containers from an orchestration.

It’s supposed to just work but jetbrains has broken it and changed the config over and over with a big regression as recently as 2022.2.

Vscode apparently handles this better.

I follow posthog, and they keep all components of their local dev env in containers _except_ the web dev and I think that’s the right move.

For my personal projects I just run services I need locally. But all CI and deployment is via orchestrated containers.
YouTube choosing not to run ad's on these videos is not censorship. Even in the days of broadcast TV networks would actually "censor" things because they didn't want them shown on their network. Also there was things that wouldn't run because no advertiser would want to run spots during the show. So let's ratchet down the drama here a bit.

A motorsports related channel should have no issues finding sponsors. I know amateur racers that find sponsors. YouTube monetization isn't even the best way to make money. Sponsors are.
You forget that Russia controls the ingress end of the pipelines. They could, and IMO almost certainly did, simply send maintenance "pigs" [1] laden with explosives and a timer down 3 of the 4 lines. No submarines necessary, they didn't even have to leave the office.

Honest question. Now that you know just how easy it was for Russia (and only Russia) to do, does that change your calculus a little?

[1] https://en.wikipedia.org/wiki/Pigging
I use these tools. I've contributed to some. The size really is as big of an issue as I think it is
On BSD systems you can press ^T for SIGINFO and that prints some progress information, at least for tools like dd and cp, not sure about cat and I don't have a BSD system to test. Linux doesn't have this unfortunately. GNU tools often support it (when run on BSD), it's just that the kernel doesn't.
It is either docker, or you will have to write an install and run/service script for every OS you are going to deploy to.

I prefer to keep target operating systems uniform, so a docker layer isn't needed. Just an install script which downloads packages and copies systemd service files needed.
What images do you use? I would love to hear about your setup to debug lambda functions.
This is like a placeholder sentence which should have been replaced with actual content.
Hype? Maybe 5 years ago, but nowadays?

> I developed containers on windows and then I still had to debug the containers when deploying on Linux. There were formatting issues, filenotfound issues, and chmod issues

You probably mean "building", not "deploying". If you've built it on windows, the container image will be the same on linux.

> I have spent so much time configuring docker, and been able to complete the same task in a VM in a fraction of the time.

Now imagine spending this time over and over and over again.

> Am I doing it wrong? Is it the case that I am not the intended audience, and it's meant for larger teams?

Have you been using tools like Vagrant or Ansimble?

I think the most general mistake is using docker "as essentially VM", with typical VM workflows, instead of a build automation and distribution tool.
Ah ha. Makes sense. Thanks for that tidbit.
A... dicktector.
Totally different scenarios
If your statement does not apply to your post, then the lines are blurry enough that your demand that people "take responsibility for it" seems far too prescriptive. Even claiming one "absolutely can't ignore it" (emphasis added) seem unsupportable.
Doesn't appear to be. Inheritance here goes under sharia law, I believe, which is a separate thing to civil law. The will is there to override the default sharia inheritance laws, and also cater for assets outside it, like crypto and foreign earnings like Google Play, PayPal. And other weird assets like Steam account.
"I'm in a similar boat. I hate Docker. I haven't used it myself..."

Different brushes for different strokes but I'm curious to know how you can hate something without having tried it? This might be understandable for something like sexuality or even types of video games, but containerisation, .devcontainers and the like. How can you hate something without trying it?

Docker doesn't shove anything under the rug and hide it in my experience, instead it surfaces reproducibility in your face and encourages you to deal with it.

What's the alternative for compilable languages short of makefiles? Even then you can't guarantee it will work on your colleagues Linux and MacOS workstations (let's ignore Windows) but that's where docker and .devcontainer shine.
People have been bemoaning Snow Leopard's demise since the first beta of Lion. Snow Leopard was a design that was internally consistent. I don't think it was the pinnacle of design, but I see why it was beloved by developers.
Why dd and not pv? dd is bundled on most distros, while pv you need to install it if you want to use it.
You can't always just go and install any packages you want on production servers.

While importing a DB dump is easy to see the progress with dd.

dd if=my.sql status=progress | mysql mydb
Apparently a kind soul bet me to it and already uploaded the files to archive.org: https://archive.org/search.php?query=creator%3A%22Shuzo+Fuji...
There's probably some contamination, but ideally it's just plastic and paper. And yah, scrubbers would handle everything else. Vinyl has chlorine which also needs to be removed.

These types of scrubbers are in use all over, it's not a new technology.

The main thing is to remove food and other organic waste, remove metals because they are useful. Glass is harmless, but also clutters up the ash, so best to remove it as well.

If it were up to me recycling would work like this:

Metal, plastic, and paper would be recycled, single stream. The metal is easily removed, the rest is burned.

Glass and organics (and everything else) would be thrown out, with some people opting to compost, I would encourage, but not require, composting. There is really no reason to recycle glass, and trying to do so causes more harm than good since it smashes and the shards get in everything and just makes it harder to make a pure product.

If you absolutely must recycle glass, it has to be in its own bin, do not single stream it.
A long as dinosaurs don't have feathers, I'm happy to have some historical inaccuracy in my entertainment.
I think you're right there - the transparency needed is from the companies, not the individuals. Otherwise it becomes a competition, and people stop sharing salary themselves because some doofus claims to be on 750k/year starting salary straight out of college.

Levels.fyi has some salary data too I think, and there's more and more being shared in Indeed and LinkedIn.
Docker on Windows absolutely sucks.

I write a lot of tools for my colleagues and I've gone out of my way to say "I can gurantee this .devcontainer will work on WSL2" and leaving my support of it there. Since even .devcontainers behave differently on Linux and Windows.
Doing Docker development on Windows eats away a lot of the benefit since you need to run Linux environments in a VM anyway. And yeah, you're going to have goofy stuff with line endings and file permissions. MacOS dev is better, partly because it's Unix-like but mostly because a lot of devs love their Macs enough to make Docker for Mac good enough.

There were supposed to be a lot of benefits to using Docker:

1. Build your environment anywhere and it will work anywhere. This is mostly true. Basic isolation of dependencies is a huge headache-solver for C/C++ development, Python apps, and anything with a complicated build chain. Go is a notable exception - the Go build process really did solve this without containers.

2. Process/resource/cgroup isolation. You can run multiple containers (even untrusted ones) on the same metal and they can't interact. It's like a VM but instead of committing fixed amounts of RAM and disk space (which mostly sits idle), you let the Linux kernel handle it dynamically with limits. At least that was the dream. But without carefully managing properties/permissions this is a security nightmare. When people say "why Kubernetes" this is one real answer. Almost no one trusts container isolation for actual security in practice.

3. Layered builds. This was a killer idea - you build your container in steps. The first few change infrequently and the last one or two is your actual app. You can ship the big OS-heavy layers once and push frequent small updates (a few MB) and still keep your dev and runtime environments identical. This breaks down a bit in the real world because a lot of people don't bother to layer things well - they wind up with 100MB-1GB monsters being pushed around endlessly. But also it kind of doesn't matter - you can push 1GB monsters on your own network/VPC all you want and it's not really a big deal.

4. Declarative builds - theoretically you can recreate a bit-identical build based on just the Dockerfile. This is great for auditing third-party images and reproducibility. Theoretically. But people forget that apt-get install on Monday might be different than apt-get install on Wednesday. Debian does security updates that way and an image built 6 months ago won't match one you build today. It still works, though, so we pretend not to notice. And sharing image layers with another host is actually kind of hard. I imagine Nix solves a lot of this but I haven't had the pleasure of learning it yet.

So Docker has fallen short on some promises and met others. But the truth is I can't think of a better way to build some fussy C project (the first thing I look for is a Dockerfile, and often it's easier to make one than pollute my system with dependencies). I also can't think of a better way to distribute a Python app. And being able to do "docker run debian:bullseye" is pretty slick. Golang is another story - I think it's very reasonable to say "what's the point?" with a go binary.
They employ over a million people. There’s going to be a pretty wide range of experiences.

I worked for AWS, it was one of the best jobs I’ve had and the only one in decades where I could leave the office, not think about work at all until I came back in, and not feel the slightest bit guilty or anxious about that. I know others have had a very different AWS experience.

Also anecdotally, I’d always chat to the facilities team/janitors at if they were in the kitchen while I was having lunch. All of them also worked shifts at the distribution center that opened up nearby. Their only complaint was they couldn’t get enough shifts there. It paid better than cleaning the kitchens in the corporate offices. Again, no doubt there’s a wide range of experiences.
Thank god. Maybe I'll finally stop getting recruitment spam from them.
Some of those apps are the worst for battery life, privacy and speed of work.
2. No, it's a statement that a correct implementation of preloading is free ignore any of your requests. So it's a net neutral.

That’s not the way the spec is written for rel=preload.

From § 4.6.7.19 Link type “preload” [1]:

The preload keyword indicates that the user agent will preemptively fetch and cache the specified resource according to the potential destination given by the as attribute (and the priority associated with the corresponding destination), as it is highly likely that the user will require this resource for the current navigation. [PRELOAD]

This sentence is quite clear:

A user agent must not delay the load event for this link type.

The point of preload is to tell the browser “hey—I know you’re busy but this resource is really important for the current page and I need you to prioritize downloading it. I know you’re not aware of this resource because you haven’t parsed that section of the HTML or CSS yet, but trust me, I need you to start downloading it right now.”

The browser is not free to “ignore the request”, which would defeat the purpose of having a directive that tells the browser you want a particular resource to jump to the head of the download queue.

There are other directives that are hints or suggestions, kind of like saying to the browser “if you’re not too busy and you have the bandwidth available, could you download this resource? I don’t need it for the current page but there’s a good chance I’ll need it for the next page the user is likely to access next. It’s not a big deal if you can’t get to it right away.”

[1]: https://html.spec.whatwg.org/multipage/links.html#link-type-...
Wow. Do you have a reference for this? That is interesting!
It just generally works poorly without large amounts of luck. Lots of counterfeit or garbage goods will work okay at first but wear out quickly or just be dangerous to operate due to cheap parts.
I don't believe it's that. On macOS Monterey:

$ which pv
pv not found

I've been using Unixes of various flavours since the 1980s and had never heard of it until I read this article. It's certainly more obscure to me – as in not discoverable at all – than dd status=progress.

Apparently I've been slumming it by watching long jobs using Activity Monitor on macOS.
I'm Gen X, part of the MTV generation, aka the Slacker generation. Quoting a quote from Wikipedia about us: "today’s students have short attention spans, lower literacy rates than previous generations, and bore easily". That was what adults thought of us.

My first video game console was in 1974, a Heathkit Pong derivative. By the early 1980s, a lot of kids in my neighborhood had Atari 400s, C64s, etc. -- mostly to play games. And video game parlors were a thing too. I would mostly watch people play, because a quarter a game was a lot.

We were the first kids to have Black History month (1970s) and observe MLK Jr. Day (1980s, for most people) - and yes, the anti-woke people of the time opposed both.

For that matter, my 1st & 2nd grade school had only desegregated about the time I was born.
"xcode-select --install" installs llvm and clang. Seems pretty easy to me!
For the past 3 years I’ve worked in an almost 100% pair programming environment. It works wonders for a lot of problems, especially around “code ownership”. It’s much harder to get precious with your code, or point fingers at someone else’s code, when the responsibility for every line is shared by at least two people.

But I found that the pressure of pairing shuts down a lot of thought. Long silences are forbidden in pairing; you must vocalize your thought process. I found myself searching for gaps in the conversation where I could think for a second and blurt out my thoughts before it’s too late to turn the train around. I believe pairing can lead to local maxima this way because there’s no room in the conversation for deep thought.
> That is life-changing money.

Yes, and it seems they used it to change their life.
I certainly agree it wouldn't have grown as big as it is with a less pragmatic approach. Entirely.

But there must be a moment when some simplicity or pragmatism must be exchanged for scalability.

Layering is one option. While indeed railroads and roads probably want to be on the same layer, opening hours or pavement need not be.
I'm not saying a node may only ever be on one layer. They can easily be duplicated over layers. Just like at boundaries of geographical chunks, (i.e. over the borders of luxembourg.osm.pbf) there are (tens) of thousands of nodes that also appear in Germany, Belgium, the Netherlands once even.
Another example:

When I open two .doc files, I can only have two separate windows or tabs. But I don't need those windows or tabs. What I actually need is just two open files on the screen. And some Word functions. From UI perspective, it can be a "function bar" on top of those two files.

If I want to open an image file and Photoshop, currently I can only have a separate Photoshop window. What I actually need is just an open image file on the screen. And some Photoshop functions - a "function bar" on top of that file.

So the visual difference is that you now have 3 different open files and some "function bars" - all in one workspace. And you can arrange or scale your files in any way you want. And you can arrange "function bars" on the screen or hide them.
It’s a vanishingly rare thing though, AFAICT.