skysight-inc/HackerNews huggingface dataset:
Yeah it does. Thanks for clarifying. I think there's a very complex conversation to be had here, especially since you're working on a meta-level of tooling to ease API development.

With two days before my first vacation of the year, my brain is a pile of mush. I'm going to politely and apologetically bow out of this conversation. =)
I hadn't even thought of this specifically, but after it was mentioned in the initial post I realized just how much that is my use case most of the time and how often I am fighting with google maps to accomplish what are relatively simple tasks like adding an additional point along a route. If you are trying to add multiple additional points on a route it gets even worse.

This is all much worse on the Android app as well, where it makes the assumption that your use case is to get from where you are right now to somewhere else. Trying to get from point A to B, where neither is where you are now, is unnecessarily frustrating.
While that's not an entirely unreasonable idea, I note that launching a browser has its own startup time. Power on to opening a document in evince is faster than power on to launching a browser, and that's support for the original thesis in a way, but it also feels like a little much to count it against "boot time".
You may well be hitting a deeper point here.

Many of the strongest AND weakest consumer technology experiences are influenced by standards in some way.

Positive Examples: pluging in an usb headset, electrical sockets, sms.

Negative examples: Trying to hook up your laptop in a random conference room, transferring a large file locally between 2 devices from different vendors.

Maybe with ever increasing conplexity and capability the annoyances fall between industry actors and solutions would need first multiple parties acknowledging the problem followed by succesful coordination.
Taking a break for them is directly losing them money. Imagine how much money a company loses by shutting down for say an entire week.

Imagine losing an entire week of revenue for the company. That's a big deal to them.

Especially because their revenue is directly dependent on their popularity. If their content isn't available, people will just move on to the next best thing.
When comparing to amber/green screen interfaces, hatred of the mouse is odd. Sure, for a simple search interface the text interface was fine-- search field, arrow down through results. But for anything more complex you end up having to tab between a dozen or more fields. ERP interfaces we're especially tedious in this regard, so the author's nostalgia for the "solved" problems of that age aren't completely warranted, and the mouse is at worst just as bad.
"Of course, no one wants to place phone calls by typing a lengthy command into their terminal"

Are you kidding ? That is all I've ever wanted to do.

I have been asking, casually, for a "gnu-phoneutils" package for several years that would give us a small phone tooling suite ...

I have largely built this out myself with twilio and, in some ways, it is no longer necessary given that I have built my own little mini-telco inside of twilio, but still ...
The other one is still on the front page…
I don't know, I can compile code perceptually instantly and get optimizations which perceptually instant compilers didn't do in 1983. I know that Turbo Pascal was very fast when it came to compiling Pascal, and I certainly appreciate the effort which went into making that happen, but Turbo Pascal didn't turn string handling code into SIMD operations after turning a recursive function into an unrolled loop.

Partly, this was due to the fact the IBM PC did not have SIMD operations in 1983, but the rest is because modern compilers run complex optimization passes in tiny fractions of a second.

Also, I'd like to see this person say that operations on computers were perceptually instant while logged into a PDP-11/70 or (let's be a tad generous) a VAX-11/780 with a half-dozen other people all trying to use it at the same time. Yes, faster computers existed in 1983. Didn't mean the likes of you got to use them.
Stamping out murder only has pushed it underground! Stamping out rape has only pushed it underground! Stamping out kidnapping has only pushed it underground! I long for the day all of these practices can be legalized and done safely and in the open!
In aggregate, search is orders of magnitude faster because it's so much more accurate. When was the last time you had to think about your search terms?

The other day I was thinking about the Baader-Meinhof phenomenon, but I couldn't remember the name of it. So I googled "when you suddenly notice something everywhere" and Baader-Meinhof was first result. Go back to 1983 (maybe even 2003) and let me know how long it takes to structure your search terms so you get the right answer.
Right, that's that point. Why does Photoshop take so long to start up and be usable even on incredibly powerful hardware?

It's hard to find an excuse, considering:

- Adobe has vast resources

- Photoshop is a mature piece of software

- It's image editing, not a complex video game (look at what something like Red Dead Redemption 2 can accomplish with every frame, @ 60FPS)
Oh definitely. Any form of coercion counts as against your will in my book.
Link to Mozilla's announcement: https://discourse.mozilla.org/t/synchronous-messaging-at-moz...
They are not too hard to find. I would use this one as a starting point:
https://github.com/neomjs/neo/tree/dev/docs/app/view
(since the docs app UI is written using neo.mjs).

On the repo you have an apps folder (RW2 is a better example) as well as an examples folder.

If you open the online examples => docs app, you can view into the code for all classes. If you use the docs app version with the Chrome flag, all available examples are included.
I've never heard this. A decade ago "white knighting" had a very different meaning on 4chan. It was used to make fun of Anons that shit on the rampant misogyny and tried to get other Anons to stop being misogynistic, and also "white knights" were people pushing for things generally socially progressive on the site.

It actually used to have a decent population of far left than far right, but now it's known only for being far right.

Crazy to see the term completely 180.
Anecdotally, we used WildFly with great success on a project or two.
> any social media job like this, be it YouTuber or Instagram influencer or whatever, seems to be all life-consuming

Isn't this older than social media? Mass media stars, e.g. post-War movie stars, were similarly all-consumed.

Maybe one has to go back to e.g. Charlie Chaplin to find an era when this kind of celebrity wasn't the norm?
The "sharp downtick" is largely a shift from "strongly agree" to "agree". That doesn't seem too sharp to me. Mostly it seems like people are happier with where JS is now. There's less momentum behind changes the language, and fewer large developer-experience-changing features coming.
That’s fair! From my perspective that’s something that’s building trust with the SaaS provider. We’ve all heard, “ugh! This API is so shitty!” before — I’m fascinated by what tools and products can be built to prevent developers from feeling these pains.

Thanks for the feedback. Can definitely see that changelogs are really underinvested in across the industry, and it’s useful to have people mention how valuable they are.
Yes, pleease, just provide Miracast or Chromecast so I can watch content from my phone on the big screen.

Or just let me use an HDMI port.

I don't watch channels anymore, and I don't want to pay for your pay-per-view content.
Hi,
Nick, can I ask you about that your 2017/2018 HFT project from another thread?
That's the first thing I disable after ever Windows 10 update (it keeps getting reset for some reason). If you have a dual-boot setup, it can result in a corrupted partition if you try to access your Windows 10 partition from another OS when fast start is enabled.
I just want to step in quick to advocate. Please do not use Qt for the web. Their web export tools aren't just unfinished, they're actively hostile to web paradigms. The finished product doesn't render to the DOM, it's completely screenreader inaccessible, it overrides browser preferences. In a lot of ways, Qt on the web is even worse than Flash was.

You know all of the arguments against Electron that people trot out about how it's not real native, and it doesn't follow the right UX conventions or paradigms? Qt on the web is exactly like Electron on native, except way worse and without any sign that it's going to improve, because fundamentally Qt is structured around the idea that it should be able to spit out a binary blob of pixels instead of hooking into web-native primitives like the DOM.

Look into something that's showing more promise, like .NET and Razor. The Rust community is also doing some good work here, although I don't know that they have any UI frameworks that are mature enough to be reliable in an enterprise setting.

These aren't true cross-platform efforts yet, since they're still forcing you to think about HTML. But if I was going to bet on any project ending up with a real cross-platform solution that felt good on the web, some kind of export option from an Open Source Windows Forms or similar is probably what I would bet on. Either Microsoft or (possibly) the Rust community are the two parties that I think are most likely to end up producing a true native UI toolkit that can actually export to the web in a usable, acceptable way.
> I've always wondered why someone may like to watch people playing videogames when you can play said videogames yourself.

I don't like it myself. But a number of my coworkers, and cousins, are of this cohort.

In general, it seems like they want an internet personality to follow. They like watching someone who gets angry and frustrated as they lose, or gets excited when they win. Its no different than following the personal lives of celebrities, except these "Twitch Celebrities" or "Youtube Celebrities" are more personalized and tailored for your specific interests.
With the recent widespread interest in Category theory I still think it's a damn shame that RDF wasn't designed to treat relationships as stand-alone entities. Perhaps property graphs work better in that regard, although it's a bit weird how properties aren't themselves relationships, but perhaps that's a necessary concession to keep things efficient.
Yeah, you need to have it, but you don't need to carry it, nor show it to anyone (including the police - they're supposed to use other method of identification if you refuse).
To give some perspective, the hourly fuel consumption for Concorde is almost identical at Mach 2 than at max subsonic speed...

And Concorde powerplant had at some point the highest overall thermal efficiency at max speed:

https://en.wikipedia.org/wiki/Rolls-Royce/Snecma_Olympus_593

The overall thermal efficiency of the engine in supersonic cruising flight (supercruise) was about 43%, which at the time was the highest figure recorded for any normal thermodynamic machine.
Two points:

They keep changing the interface faster than I can learn it.

The way to enable complex expression of tasks in a user interface is by composition. ie have microtasks that you can then combine in different ways.

That's what makes excel great - each cell is a single function but you can combine them to build stuff the developer never knew was possible.

Being able to store state ( a location ) and then operate on that state is a pretty basic building block of a composable map UI.
I'm not sure what you're talking about. I suppose we have different backgrounds.

- I've never heard a single ranking officer in the army or intelligence circle or the judiciary branch ever claim that "it's not clear that secrets are necessary" — you'd be right many don't think it's an evil though. (I've personally interviewed such people among others for research, many times between 2006-2014, and this question was central to some discussions because we were indeed designing political regimes).

- You seem to confuse "secrets", the general idea of hidden information (e.g. a Christmas gift, the location of a weapons repository, the name of a lover) with secrets as a security device (PIN codes, passwords, the layout of a physical key). The former are content, the latter are means to restrict access (meaningless in and of themselves). You seem to argue that the latter can do better with less "remembering" (security practices, FIDO, etc), and sure go for it; but that has nothing to do with the former, actual secret information (content) which you seek to protect by way of such security devices.

- My point was about secrecy as a function of States, well before digital computers even existed, and well after. Modern computing compounds effects but doesn't change the nature of institutions. You'll always need to secure 'dangerous' stuff. I'm not sure how you envision a hostile invading army on your ground, but if you picture that suddenly many red lines appear clearly.

I'll tell you the dirty secret: the less they have an actual enemy to fight, the more they idle, the more "these people who desire secrets" become threats to the wider population — people report that it's such a parallel world view as an insider that focus can get fuzzy, undetermined, self-harming. This is why historically you see many governments pretty much making up enemies: a mundane observer would tell you it's to a classic to unite the population (or your base versus rival groups), but a historical perspective shows it's also to curb the 'natural deviance' of all the shadowy things in a State, to focus them for good when their idling becomes too evil.

None of this black and white. Nothing's fundamentally changed with computers or electronics — it's more game theory, math, and obviously philosophy, psychology, than whatever implementation of a system throughout history.

For another round at not-so-simple-secrecy-management, consider now corporations, first between them, then in interaction with States. You'd think it's all new, unseen before. Go read some account of the 16th century or even before. See how this is just part of human nature. As I tell myself, "deal with it".
I don't have the numbers on hand, but it's likely even more drastic.

The original blog post has long since been deleting (https://theblog.okcupid.com/your-looks-and-your-inbox-8715c0...), but according to one of the OKCupid founders:

> [Women] rate a whopping 80% of men on the site as ‘below average’.

You can imagine that people aren't swiping for "average", so the selected percentage would be even less.

Link: https://techcrunch.com/2009/11/18/okcupid-inbox-attractive/
>
Exactly. It does placate users with some indication of activity. [...] One thing it does do is confirm the change is in progress.

A black screen is also a sign that a change is in progress. But this is exactly what my parent fortran77 complained about (https://news.ycombinator.com/item?id=21835676).
I complained about the style of the article elsewhere in the thread, but this doesn't exactly disprove the point that it's objectively worse now.
FWIW, this segfaults CPython in 2 lines:

import ctypes
ctypes.cast(1, ctypes.py_object)

Interestingly, this works:

import ctypes, gc
x = 22
_id = id(x)
del x
gc.collect()
y = ctypes.cast(_id, ctypes.py_object).value
assert y == 22
Yes, everyone has a smartphone on them. My healthcare system has policies that say smartphones aren't allowed in patient care areas, but that isn't followed or enforced. Physicians definitely have phone since many use app for clinical care (there are a lot of online risk calculators, reference materials etc).
Maybe there's not a lot you could have done while keeping the hardware cheap. I can think of a few ways to improve the user experience of channel surfing without waiting for an i-frame every time.

The cheapest would be to just use a constant neutral-grey i-frame whenever the channel flips, and update that until a real i-frame comes along, while playing the channel audio immediately. Ugly video for a second, but high-action scenes fill in faster. I'd bet that most people could identify an already-watched movie or series before an i-frame comes in, at least 80% of the time.

More expensive would be to cache incoming i-frames of channels adjacent to the viewed channel, and use the cached image instead of the grey frame. Looks like a digital channel dropping update frames during a thunderstorm for a second.

Prohibitively expensive (back then) would be to use multiple tuners that tune in to channels adjacent to the viewed channel, and then swap the active video and audio when the channel up or channel down buttons are pressed. Drop the channels that just exited the surfing window, and tune in to the ones that just entered it. Surfing speed limited by number of tuners.

Televisions still don't do this, even after more than a decade of digital broadcast, and multiple-tuner, multiple-output DVR boxes.
The guys say that death by asthma (severe cases certainly) are gently falling, but it looks pretty flat to me.

https://www.cdc.gov/asthma/asthma_stats/asthma_underlying_de...

Do you have any intuition for how to identify an increased willingness to over-diagnose? It may be true, but how do we test this hypothesis?
Well said! But the difficulty lies in convincing people that you are in the latter and not in the former group :-)
fascinating, thanks for this post.
I prefer to see it as continuing the argument in the same tone as the original - ie not particularly truthful and set in tone and content to support a skewed point of view and appeal to sentiment rather than anything else.
Neatbash – A Simple Bash Prettyprinter
One one hand, I like a nice long commit message. On the other hand, human nature is terrible.

I know that if long commit messages catch on, some synergetic managers will start insisting on minimum lengths for commit messages, and start having meetings discussing standards and policies for commit messages, and start filling binders with more rules than one person could ever memorize. Soon, fixing a single-character typo in a comment will take 20 minutes, and pressing enter will be nerve-racking because you know there's just something you're forgetting from the binder.
At about the same time, Chris Beams wrote this, which I have loved ever since:

https://chris.beams.io/posts/git-commit/

I note with some glee that magit colorizes my commit text and flags long lines,etc. largely in the style of this advice.

The money:

The seven rules of a great Git commit message

Keep in mind: This has all been said before.

Separate subject from body with a blank line

Limit the subject line to 50 characters

Capitalize the subject line

Do not end the subject line with a period

Use the imperative mood in the subject line

Wrap the body at 72 characters

Use the body to explain what and why vs. how*
This also reminds me of the conspiracy perpetrated by the industry to remove the antiglare treatment of laptop screens and at the same time reduce the screen area by changing the aspect ratio. All this, of course, was done solely for the benefit of the consumer. (Oh, that, and a wild ornament around the keyboard.)
Let's not forget that "computer" was a job mainly done by women. The name "personal computer" is telling, just look at the games from the era when PCs were new, to understand what was in the mind of those privileged teen males. It is not surprising at all that now the same people come with "supremacy", a word which could be easily replaced by "slowness challenged".
It is absolutely nuts that we don't have a greater diversity of computing platforms (as we did in 80s 90s) considering we have such widely adopted standards today that overcome the "compatibility" problems. There's fertile ground for exploring more Smalltalk/Oberon/Hypercard/Lisp-machine like computing systems, with the confidence that they will be able to interact in a meaningful way with the outside world.

Unfortunately, Computer Science continues to train people in Unix.
Nice, given how the discussions were going some months ago I was worried that they would pick some closed source solution like Discord or Slack. I have not used Matrix so I do not know how good it is, but I do not like the lock-in of Discord and Slack.
> When a channel is switched, the TV has to wait for the next I-frame, since P-frames (and B-frames) only encode the difference to the previous I-frame (or to the previous and next I-frame in the case of B-frames).

You can apply the encoded difference to a grey (or black!) screen, the way (IIRC) VLC does in such cases. This means that the user immediately gets a hint of what's happening onscreen, especially since the audio can start playing immediately (also, often the P/B-frames replace a large portion of the on-screen content as people move around, etc.). Surely it isn't any worse than analog TV "snow".

If it looks too weird for the average user, make it an "advanced" option - 'quick' channel changes or something.
Rust 1.40
After being in the field for almost a decade now and guilty of so many poor commit messages, I came to the firm realization that a very important trait of a good software engineer is the ability and diligence to write detailed commit messages, and I would have never remotely imagined this during the first few years of my career (I was "raised" in companies who didn't care at all about this and all commits were always "add x", "fix foo", "fix build", ...). It became way too frustrating when I looked back at code committed by myself (or others) years prior and wondered "what is the reason why this code exists?"

These days, every single commit I push has an entire paragraph or two clearly describing the changes, and the motivation behind them, even if it's a one-line diff.

My team praises me for this, and I think I've been able to influence the culture as I see more junior people taking their time to craft good commit messages and edit their commit history before pushing a PR.
That's hilarious. The way to privacy is to ... wander around naked, because male nudity is outside the commoditisation zone?
Where Are the Tech Zillionaires? San Francisco Faces the IPO Fizzle
> Before Electron people had the arguments about bloated apps when it came to WPF and Qt.

which is funny when you see that Qt runs on microcontrollers now.
Ah, the same Nickle's Worth who said (iirc), "Europeans call me by name. Americans call me by value."
Reviewing Pull Requests
> Expect worse taxiing, take-off and climb fuel economy, due to dense air and also suboptimal (high) angle of attack.

This reminds me, in the book "Skunk Works", SR-71 Blackbird pilots mentioned their schedule of mid-air refueling 20-30min after takeoff. After that they could make it 3-5hrs at high altitude before refueling again.
Buy a personal HEPA air filter on Amazon and get purified water delivered. Quit trusting your city officials with your health.
This seems to be conflating several separate problems

1) I can't manipulate data in my resultset well enough in google map.

2) Searches are too slow.

3) Mousing is bad.

Now, you can argue that those are related.

The first two are an argument for moving away from full-page post/response applications to SPA-style applications where the data is all in browser memory and as you manipulate it you're doing stuff on the client and pulling data from the server as needed, desktop style.

The latter? I don't know why he had to go back to DOS guis. Plenty of windowed UIs are very keyboard friendly. Tab indexes, hotkeys, etc.

> GUIs are in no way more intuitive than keyboard interfaces using function keys such as the POS I posted earlier. Nor do they need to be.

This is where he loses me. I remember the days of keyboard UIs. They almost all suffered from being opaque. You can't say "the problem is opaque UIs" when that describes the vast majority of keyboard-based UIs.

While there are obviously ways to create exceptions, GUIs are intrinsically more self-documenting than keyboard inputs, because GUIs require that the UI be presented on the screen to the user, and keyboard inputs do not.