skysight-inc/HackerNews huggingface dataset:
Point well made that quite often, "the right thing" and "protect the company" are the same, because "protect the abuser" is not good for the company, good publicity etc.

However, people often act for short term gain at the cost of long-term pain. I think that it's fair to say that Uber did when they repeatedly tried to "make the problem go away".
I accidentally wrote a fork bomb in a shell script last week. It went like this:

foo() {
echo "$1" | foo
}

Then called foo later. The 2nd occurrence of foo was a typo for something with a very similar name. Took me a few reboots before I realized this.

I find this a bit more interesting than the cited shell example because it does not involve the & token. Just pipes.
My printer says it requires that. But it works fine with the free drivers included in my package manager when I pick some other random printer model.
To put a face on the problem, this video of an orangutan fighting to remain in its home while the forest is logged out from under it is powerful.

https://www.youtube.com/watch?v=ihPfB30YT_c
Indeed!

Also https://www.youtube.com/user/mikeselectricstuff/videos for lighting and scrap medical/industrial equipment teardowns.

If you are into RF dark magic, https://www.youtube.com/user/TheSignalPathBlog/videos for teardowns (and repairs!) of GHz scopes, network analyzers, etc.
Even if true, our computers are able to access many, many, many orders of magnitude of information than my computer could in 1983. What my computer can do for me today is probably 1,000 times more valuable to me than what my computer could do in 1983.

If it takes being slower, I'll take that tradeoff in a heartbeat.

(But I also remember it taking up to a couple minutes to load a program from a floppy, so there's also that.)
Show HN: AI Business Name Generator
In terms of climate change, palm oil seems to be a really really bad substitute for other oils. I'd support increased tariffs on palm oil, and moneys to subsidize keeping rain forest.
And it's probably going to get worse with wasm + canvas.
This is more or less my preferred solution. I use z-wave switches, not modules, though. I don't get RGB control, but I do get home automation that fails gracefully back to "works just like a light switch always did" if something goes wrong.
In my experience this usually boils down to different opinions on design decisions or the best way to implement a feature. One way to mitigate is to hold a design review where you get their sign off before the PR. Outline the basic strategy and pseudo-code. Document the functional interfaces etc...

The other thing to do is to ask for specific feedback to get to the root cause of the disagreement. I try to disarm them by agreeing that the code "smells" but it was the best you could do given the constraints. Does this developer "own" the code (is it their baby) or product you are working on? Ask what they would do... you can't mind read after all.

If you've built group consensus first then the negative reviewer has less room to maneuver as well.

Next consider proposing that the group create a code review protocol. This is similar to a coding style convention. Try to get consensus and sign off.

Lastly, check out the 5 secrets to effective communication, they really work. It's takes a lot of practice though.

https://feelinggood.com/2016/12/12/014-the-five-secrets-of-e...
You can choose to get your AirPods engraved when you order them. It doesn't cost anything extra so you might as well engrave something funny.
Reminds me of the Jevons Paradox.

It's so efficient to produce that it's worth blanketing whole tropics in palm oil plantations to maximize the economic productivity of developing countries... https://en.wikipedia.org/wiki/Jevons_paradox

(I'm not a huge fan of biofuels for this reason.)
a hypothetical global catastrophic scenario involving molecular nanotechnology in which out-of-control self-replicating machines consume all biomass on Earth while building more of themselves

It’s right there in the first sentence. Nothing about eating concrete or sand.
Story time: I once worked part time with a company, and their DBA was doing a project to look up all the IP addresses that had been logged into one of their database tables. For every address he was running a bash script to do the reverse lookup.

This was going to take a few days to run, largely because it was forking 10-20 times for every IP address, most of the lookups themselves were fairly quick (though some weren't). I explained to him that forks are fairly expensive operations, and every line in his shell script was 1+ forks.

I thought this would be an easy win, I picked up a multi-threaded DNS lookup tool and showed him that it could look up a thousand addresses in < a second. "Oh, so I can just replace the "nslookup" with this other program in my script?"

I explained that he would need to make a file with all the IP addresses he needed to look up, I'd run the program on a server at our data center (to not clog the office T1), and then I'd give him back a file containing "address,name".

"Oh... So I'd have to correlate each address to a name myself? I can't do that, I need to run this script." In my head I said "You're the DBA, how can you NOT correlate this data?"
Worse, that type of thing is long been known as an dangerous issue and the industry has processes and protocols to deal with it. That's why it's "worse", Boeing knows about all these things and conscientiously decides to don't give a f#$%k.

Airbus ( and I'm sure pretty much all the other manufacturers ) has all the processes for training the workers about this problem, how to avoid it, how to deal with it when happens, check-in and checkout all the tools at the start and the end of the task, inspections, etc. this is so basic it hurts.
I am sure that Microsoft Autoroute was available for that era. It probably was also faster then Google Maps is today.
Right... or it can be even slooooower, you can watch a full "V" episode if you have a Datasette.

As you point out, the waiting times were not in the seconds but in the two digit minutes.
I don't have IRC :)

What I will say is: I think the technical side is the easy part. Just serving static content. The hard part, which is also much less fun, is the business side of acquiring customers who want to advertise. Not only is there a bit of a chicken-and-egg problem, it'd require marketing, negotiating, maybe inroads in certain circles, knowledge of the market, etc. That's the point at which I decided I didn't want to mess with it haha.
Google Maps is great for A to B. I love it. Use it even if I know the route since traffic can be a pain. It appears fast for me. I'm very much disconnected from what the post says. I've used DOS, Windows 3.1, Windows 95 and so on. Now I'm on Mac and Fedora. Never will look back.

Let's remember here that most operations were executed against a cache of data on the local system. That cache is way too big to store on the local system nowadays, so of course we are going contact a server to perform the operations and we will experience network latency that will vary. US internet speed has stagnated. Some time in the future, if typical ISPs don't get their way and we get faster and faster connection speed then these latency complaints will be irrelevant.

Developers could do better in sending less data in general, but that will take more time. Does product management care much about latency if they are not given the mandate? We seem to all want features and more features, but less of the cruft that follows as a result of development, which is weird. Best way to vote in the end is to just build your own application however you can. Waze's features would have never made it into Google Maps if users were not using them instead of Google Maps.
I do the same with the iron, but first i melt a bit of fresh solder on.
Raspberry Pi 4: Chronicling the Desktop Experience – Retro Gaming – Week 17
Meet the Germans: Why is it taking Germany so long to go digital?
The "division of thought" you talk about is the opposite of "opinionated" designs/standards.

The former assumes that the reader is going to take their time, think about their own implementation and their own specific use case, and make several careful decisions about how to make it work.

The latter assumes that ain't no reader got time fo dat, and is going to try to npm install any packages that have the same name as keywords in the title of your standard and assume that they're fine.

Development these days is unfortunately slanted towards the latter at a lot of companies who only measure output on number of features you've shipped or the impact of products you've launched, so every incentive there is to ship things as soon as you can.

However, there's no field in package repository metadata that says "this package has sharp edges, use with care" or "this package comes with safe defaults, but use with care nonetheless".
Yeah the IRS budget has been intentionally slashed over the years to make their job enforcing the tax code harder. It's part of why they go after low return audits on low or middle income people so much more than against corporations and the rich, rich people and corporations have the money to hire lawyers to draw out cases where poorer people don't so auditing 10 Etna's is 100x easier than going after a company with a complicated tax evasion scheme.
It turns out that that "window dressing" is by far the most practically useful part of functional languages.
With browsers the network latency caps the speed ultimately, no matter how fast a CPU you have. Also HDD/SSDs are very slow compared to the CPU caches. Granted PCs of the previous era also had the same limitation but their processors were not fast enough to run a browser 400 times faster if only the HDD wasn't there.

But other simpler programs should be very much faster. That they perceptually aren't is because (IMO) code size and data size has increased almost exponentially while CPU caches and main memory speeds haven't kept up.
> What I guess I am trying to say is that this kind of vile behavior is in fact pretty common, unfortunately, and also not necessarily only something men do to women (although I am sure it is more prevalent in that direction). But most of it I wouldn't attribute it to sexism, but to assholes being assholes.

So it's true that being propositioned for sex by someone who has authority over you is not something exclusively suffered by women. And the fact that it happens more often to women than men at Uber may not necessarily an issue of "malicious" sexism, since it just so happens that men in Uber management far outnumber the women.

What elevates Fowler's scenario is the systematic responses by HR and other management to ignore or otherwise suppress this issue, with Fowler and with many of the colleagues she talked to. After Fowler thoroughly documented this first incident, an ostensibly non-sexist HR/management would sanction the manager, not Fowler [0]:

> Upper management told me that he "was a high performer" (i.e. had stellar performance reviews from his superiors) and they wouldn't feel comfortable punishing him for what was probably just an innocent mistake on his part. I was then told that I had to make a choice: (i) I could either go and find another team and then never have to interact with this man again, or (ii) I could stay on the team, but I would have to understand that he would most likely give me a poor performance review when review time came around, and there was nothing they could do about that

The second excerpt I quoted in my prior comment indicates that, according to Fowler, a sexist mindset had become enshrined in management's decision-making:

> When I pointed out how few women were in SRE, she recounted with a story about how sometimes certain people of certain genders and ethnic backgrounds were better suited for some jobs than others, so I shouldn't be surprised by the gender ratios in engineering. Our meeting ended with her berating me about keeping email records of things, and told me it was unprofessional to report things via email to HR.

[0] https://www.susanjfowler.com/blog/2017/2/19/reflecting-on-on...
The most practical way to give these ideas an opportunity to grow (IMO), is to start with code. Rather than code being stored as text, we store it as "objects" (as described in the article). To the extent which you are already using high quality tooling we already get many of these benefits, with the unfortunate addition of tons of parsing code duplicated between your compiler/interpreter, ide, text editor (syntax highlighting), and other tools (refactoring, etc.), as well even more duplicate code covering the mechanics of the internal model of the language(s) you are using (linters, intellisense, etc.).
> Surely this is more about political coercion than tax?

What's the difference? It good anyway for the US because it would set an important precedent for future litigation on the matter of profit offshoring.
Regardless of any particular politics, they seem like a politically expedient target. Everybody hates them (while using their products, which is funny), and they aren't a big government contractor.
They're probably useful in long term and not so obvious ways we won't figure out until it's too late.
May be I was unclear. If we introduce record abstraction for file ops then OS low-level implementation have to decide which way to store structured data. meta + payload or meta separated from payload. In latter case there is no way to provide fast record streams. Former case does not allow fast byte streams. Client decision to receive bytes or records doesn't magically zero copy reorder stored data.
>Taxpayer money spent on a brazenly partisan political campaign.

You should come to Catalonia...
As an amateur radio operator, I can hear the RFI generated from that cheap bulb just by looking at it. I upgraded my home from CFL to LED and found out the hard way that cheap IKEA bulbs are not conducive to a radio hobby. Philips Hue and Lifx have been generally much better.
Probably mostly ACKs.
Skunkworks Project
I’m neutral on this, but if I had to guess: @DHH shed light on it via his twitter recently in a big way.
I make a point of _not_ buying palm oil, by reading the ingredients list as I'm shopping and sticking to brands I know behave. When reading this thread, I went and checked my cupboard only to find out that my peanut butter [0] contains palm oil. Turns out only _some_ of the peanut butter made by that company has no palm oil [1], and while I would normally buy the 100% peanut, I stuck to the same brand when it wasn't available and ended up with Palm Oil.

[0] https://shop.wholeearthfoods.com/products/whole-earth-origin...
[1] https://shop.wholeearthfoods.com/products/whole-earth-100-nu...
Hi, I'm the author of the piece, perhaps better known here as founder of CoderPad. Feel free to ask me anything but things are a bit crazy right now!
Big thanks twitter! You really never suprise me any positive actions. So sad that we have big tech companies like that existing today.

I'm ditching twitter long time ago.. too much sensor and negativity from that company.
> So if I'm being "elitist" to point out that spyware is a bad thing, then I'll happily accept that moniker.

The article isn't talking about spyware. It's a chuntering rant about "Kids these days" with no analysis of why things are the way they are. Spyware doesn't fit, because it's doing exactly what it's meant to do, and the question of whether it pisses you off is secondary at best as long as you're convinced there's no alternative to the kinds of software which bundles spyware as part of you getting what you pay for.
Ah, how quickly the Internet forgets. .dev wasn’t going to be open for the rest of us originally; Google bought it as an internal name to keep private but relented a few years later.

> The web ad giant is keeping these domains "completely closed for the sole use of Google," as its paperwork filed[0] for .dev reads.

> Why not also share the wealth of .dev with developers? Well, in a word: branding. Google's successful application for .dev reads: "The proposed gTLD will provide Google with direct association to the term 'dev', which is an abbreviation of the word 'development'. The mission of this gTLD, .dev, is to provide a dedicated domain space in which Google can enact second-level domains specific to its projects in development."

https://www.theregister.co.uk/2015/03/13/google_developer_gt...

0 - https://gtldresult.icann.org/applicationstatus/applicationde...
> While dealing with autoexec.bat and random BSODs wasn't fun, it's entirely orthogonal to the fact that a DOS-era POS still offers orders of magnitude better UX than current-era browser POSes, or than most web apps for that matter.

These aren't orthogonal in any way. A significant chunk of modern performance hit relative to older Von Neumann architectures is the cross-validation, security models, encapsulation, abstraction, and standardization that make BSODs an extremely unexpected event indicative of your hardware physically malfunctioning that they have become (as opposed to "Oops, Adobe reverse-engineered a standard API call and botched forcing bytes directly into it when bypassing the call library's sanity-checking; time to hard-lock the whole machine because that's the only way we can deal with common errors in this shared-memory, shared-resource computing architecture!").
Once your firm gets a set office space, what layout plan will it have?
Not sure why you are getting downvoted. From layman perspective, registering a small company with the govt, they do charge fees right?
You lose half of the possible steps in RGB mode (128 instead of 256), but a change of 2 is hardly noticeable when painting, even when applied to all three channels.
I would love if the not operator is usable instead of ! in other places than pattern matching. It's something I've wanted for a long time.
Singapore has a public operations dashboard for COVID-19
Perfectly fine, not. Ryzen laptops at least blow away all Intel Desktops, but older laptops were still better. At least Fedora caught up after the GNOME 3 desaster, with Wayland and better kernel's.
The new ones are now almost as good as a 2012 MacAir.
Yep.

PRESS PLAY ON TAPE

Might as well go walk the dog.
It's a coincidence. I was working on the story for five months, but some recent student unrest catalyzed Kate Clark's (excellent) reporting.
> Taken to the extreme, a sufficiently advanced AI compression system could theoretically end up storing representations of high-level features like faces in the compressed data

Or, you could have a compression system created specifically for photographic images (as opposed to a “general compressor” like LZ77), where these high-level features are part of the (de)compressor itself.

Now, lossy domain-specific compressors are pretty common; one good example is audio “voice codecs” for telecom, in which every snippet of audio is encoded as a phoneme-like symbol, such that noise comes out the other end as a gobbledygook that sounds a lot like words.

But much more interesting to me is a lossless domain-specific compressor, which I’m not aware of any examples of. (Please tell me if about some if you know them!) In such a compressor, the input would be “rebased” against the model, such that the output looks like an instruction stream ala “start with [this synthesized template with these parameters]; and then add point-modifications {A, B, C, ...} to get from there back to the original input.” So inputs that were more like something it “understood” would compress well (i.e. just be described by a template) while inputs that were less-well-understood wouldn’t get much from the procedural-generation phase, and would end up being specified entirely as point-corrections, and so not really compress at all.
Could also be fixture choice. My Feit can lights from Costco have had a couple failures so far, a few years after I bought them, but mostly when I have an LED bulb fail it's been in one of my enclosed fixtures. That's my choice, though, I take the risk. I buy decent quality bulbs, but I like them bright so I end up with 1600 lumen bulbs in an enclosed fixture, which is toasty. They only last a couple years before malfunctioning. Sometimes I can get more time out of them by moving them to table lamps.

I monitor the electric service at my house and it's very steady at 240V.
Then use a different method of validation, like DNS?
> Would you really rather be some other gender and/or race? Do you truly believe it would make life easier?

Yes, I do believe so. I've had jobs where women earned more just because of their gender. They were inexperienced as fuck, needed help with basic tasks and still got paid more.

Women can get an IT-job because they are women, men can't.
That's the major usecase for mobile GMaps, because it absolutely sucks for any other usecase, and thus people can't use it for any other purposes really. Except maybe looking up timetables for a previously known public transport stop (only in certain countries, some have much superior ways to plan public transport travel); planning a transport between two stops if you're not standing at one of them right now probably requires a phd.

Also if your mapping app is good, the people will use it as little as possible. That's certainly my desire as a turist. So maybe perverse incentives are at play, if wrong usage metrics are used to improve the app.

Anyway, I'm used to using paper maps from the childhood, so ergonomics of mobile phone apps is really irritating, because of how paper maps work so much better for me most of the time.
Your point about Linux GUIs is quite true. I've found DEs like Gnome and KDE to be more resource intensive and klunky. Some 8 years back, there was only one distro (I forget the name) that used FluxBox that was blazingly responsive but lacked intuitiveness. (I've heard i3 is also very fast, but I have never used it as I don't like tiling WM).

Before corporates entered the Linux market (e.g., Red Hat and Canonical), Linux actually used to be faster than Windows. Today, I find Ubuntu (and most Ubuntu based distros) to be equal or sometimes worse than Windows on the same hardware. It just feels as "weighed down" as Windows.

And yeah, you are absolutely right about BeOS - it felt revolutionary to run two sessions of a movie player on a 200Mhz powered system with 16 MB ram!
This is exactly the contract that has caused the issue. I asked for the agreed fee for my IP under the terms of the contract.
Ah, sorry. Totally missed the context of your comment.
I've seen discontent with Lambda brewing on twitters for quite some time:

https://twitter.com/KeziyahL/status/1155154616281178114
I can’t afford to do this more often but I once threw an iPhone against a wall. It felt really good and the phone still worked :)
Because they can take a cut of that money for themselves.
Change Request Size
About printers, it depends on manufacturer. Some printers are easy to setup. I know at the places I used to work whenever I went to printer setup and network I would see the printer very easily.

They say the fastest code is the code not written. I say the best printing is not needing it. I don't have a printer since I only need to print things every once in a while (few times a year). Whenever I need to print, I grab my usb stick put what I need on it and drive off to FedEx or UPS and print out what I need. Point and click, very simple. Cost of printers haven't justified buying one for me since it is a couple cents per year.
Your correct of course. The 767 refueling plane has been on hold for almost a year since the Air Force kept finding random parts strewn all over the plane.

Many airlines will not accept the 787 built on the east coast until they are flown to Seattle to be inspected there first.
As a former USMC grunt with multiple combat deployments this is spot on.

I try cutting slack here or on Reddit but most of the time when these topics come up you can tell nobody has any clue what war is like.
SBCs for Chrome OS