skysight-inc/HackerNews huggingface dataset:
If most UX designers took the time to listen and understand people's needs, then this wouldn't be such an issue. But in my experience, there is a culture of hubris in the UX community.

I doubt most UX designers have ever even used a curses based interface. They are just disgusted by seeing so much monospace text, and are compelled to tear it down and replace it with something they are comfortable with (And usually the only thing they know how to use).

I had to clean up after some UX monkeys a few years ago, who "upgraded" a warehouse inventory system. The warehouse used 30 year old embedded MSDOS based portable Symbol terminals and a SCO UNIX server in the back end. They also used Wyse terminals in the office for the admin interface and data entry. Everything booted in seconds, and the portable terminal/scanners lasted for days, and never had a problem.

They decided to replace it with React Native on Android touch screen terminals (this was a refrigerated food warehouse). The hardware couldn't go even a whole day, and the touchscreens were not at all appropriate. The software was slow and unreliable, and had led to costly mistakes.

Speaking to the designer, he seemed far more concerned about how it looked than about adding back essential features. He kept joking about how backward things had been, and how heroic he was for helping these simpletons see the light. His only justification for several things was that it was "trending" and he didn't want his client to be "left behind".

They also started by gutting essential features, and adding them back on a rolling basis, when they got around to it.

In my opinion, a big part of the problem is the culture of UX. It seems to have amplified the stereotypical arrogance that people sometimes associate with IT people, and combined it with smug fashionistas.
It's not, that's C++.

Rust requires a lot of runtime checks, but that's the price one has to pay for memory safety.
"resource scarcity is the mother of quality code"

I don't know, your mileage may vary with this one. I have had to make code less readable to make it more efficient more often than I've been forced to find a more elegant way because the clever hack was too slow.
The tweet basically links to the blog post https://victorzhou.com/blog/properly-size-images/

"Please submit the original source. If a post reports on something found on another site, submit the latter." https://news.ycombinator.com/newsguidelines.html
I've come across code on IBM System i (AS/400) with copyrights from the late 70's. The code still works, plenty of businesses run on it, and it was written quite nicely.
It's really useful to have access to an eval() function when paused in a debugger. That alone makes this useful -- it'd be great to have IDE's like Goland take advantage of this to provide this functionality.
Honestly my biggest frustration with this is how much a complete waste of resources this is. The same practical effect could be achieved by installing the trackers/whatever on the outskirts of a standard door, replacing the price labels with 7 segments LEDs, and beefing up the glass insulation a bit; instead we are slapping a giant custom screen that has to be powered 24/7 over the mess that's probably going to end up more fragile than the average phone and uses more rare-earth's than the tesla parked outside.
Did anyone expect more from these devices? It like expecting privacy from virtual assistants.
That is an interesting point I had never considered.
Nimiq Makes Fiat Currencies Blockchain-Compatible
I’ve recently started opening the large java project at work in emacs because I didn’t want to deal with how many resources IntelliJ uses when I start it up with a huge Java project.
I was going to disagree with you, but after thinking about it I don't think I do.

Vim is a great program that would completely shit the bed if stdout was a printer. However, vim's interface is shit, regardless of how well it works after using it long enough. It's notoriously hard to learn, and the vast majority of non-programming users, IMX, know enough to open a file, make a modification, and save it. Vim would be better if it had a GUI (one more extensive than gVim); that's exactly why SublimeText, Atom, Visual Studio Code, etc. are all so popular. They're vim (they all have vim key extensions), but with the GUI that makes them easier to learn and use. No, they don't have a perfect analog for that one super obscure feature that only you ever use even though you tell other people how great it is all the time, but that's because they're newer programs with fewer features, not because they have a worse interface.

Even programs like top really work better as a GUI. Being able to sort and scroll the list easily, or get contextual information from a process with the mouse is better. Top is good, but it's limited, and not a substitute for a more complete process monitor.
The original comment was about the regularity of updates and the complaint that Windows requires reboots more often. The op then compared his Linux Server's uptime to his Windows Desktop.

I simply said that wasn't a fair comparison because Windows Server doesn't require you to reboot.

You guys are arguing that Linux is Linux and I'm not disagreeing with you. Linux loads executable into memory before running them, Windows doesn't. So files on Linux can be updated/overwritten without reboot. That's a technical hurdle that can't easily be overcome.

The downside of that feature is that it's a hell of a lot easier to have a Linux system not come back up when it reboots because of drive failures or corruption. I've had that bite me in the ass a handful of times.

Regardless, my point was that if you need a system to have ridiculous uptime there is a version of Windows for that. I would argue that you absolutely do not need your laptop to be up for 3 months at a time.
More Michigan startups like Rivian are growing into rare unicorns
Dividing 1 by 998,001 Yields a Strange Decimal
Relative to Western Europe, everything from Los Angeles to Las Vegas is in the Mojave Desert. The desert is the size of Portugal. Death Valley National Park itself is an uninhabited region 1/3 the size of Switzerland. Even if it wasn't desert, and even if it wasn't mountainous, getting stranded there would be life threatening. But of course there are mountains and desert and heat.

The root cause, to me, was normal complacency. Looking at a map and not taking the words "Death Valley" seriously. Seeing 500km from Los Angeles to Las Vegas and planning like it's Berlin to Munich. Everything else in the tragedy stems from that. We all do it. Looking at the bottle with a skull and crossbones and doubting it's seriousness because day to day our lives don't include bottles of poison. We're conditioned assume Death Valley is ironic branding by a tourist board based our everyday media experience.

Interpreting the tragedy as a series of small mistakes is attractive. But the article's story is all about not making the fundamental mistake of taking Death Valley lightly...and even then it's full of near disasters where the experienced search and rescue operators almost take it too lightly and come closer to the envelope than intended simply because 99% reliable isn't 100%, because of the weather, and because there's no one around.
I would still feel shame, to the extent that the bankruptcy was due to my choices. I would judge others on the same basis.
Or take the best of both worlds with VIM IntelliJ plugin :D.
To piggy back, this also goes down the dependency chain. Leftpad wasn't bad because it was being used directly. Projects imported other libraries which either directly pulled leftpad or, more likely, pulled another library which may be the calling party or not.
At this point seeing "cs fundamentals" looks like an age discrimination red flag to me.
jq has made it easier to munge complex data from many non-unixy apps, but then you have to learn how to write complex jq expressions. Something like sql applied to json might make this easier.
> memory/resource scarcity is the mother of quality code

My experience with Legacy code has been the exact opposite of this. I've seen some really well written and documented legacy code but almost never in resource / performance sensitive areas.

People inevitably seem to accept trade-offs that sacrifice readability and maintainability for efficiency.
Long before DVDs, CDs and diskettes in magazines were a thing we had playable records as attachments. They were not real vinyl, I guess, but out of flexible plastic. The ones I remember were about the size of a single but square and also just one-sided.
Not to get off topic here, but banks were bailed out because they made subprime housing loans that went bad, however it was the government that compelled those loans in the first place. By doing what the government demanded (increasing home loans to people who didn’t have the proper credit,) the banks crashed. Government policy and housing “activists” created the housing collapse.

https://fee.org/articles/how-the-federal-government-created-...
Exactly. That sounded nothing like clinical depression. That was a shitty few months that he fixed by getting a new job and paying off a massive debt.
Hopefully there's even odds it will be a woman by then.
The implicit promise was "I will act lawfully, which means that I will do my best to repay; however, if I find I am unable to repay, I will lawfully use the legal recourse for this situation, bankruptcy". It was not broken.

One can't just declare themselves bankrupt - you have to go through the legal system to do that, which supposedly verifies that you indeed qualify for the protections afforded by bankruptcy. Note that this is the same legal system that enforces the lender's rights in case you are able to repay but will not.
Seem bizarre to push being only four times faster than straight lua when it is compiled to native instructions. Lua is 50x-100x slower than a native binary.
This corroborates how I got out of my own depression. No episode in particular caused it, just growing up around shitty people that mined my self-confidence and social skills.

How did I get out of it? Just like the author, a switch flipped. I could keep the status quo and be miserable, or I could do something about It. Read that again: We require a definition of "It".

I did therapy for years, which helped me learn how to organize my feelings and know myself better. What happened is that eventually I was able to identify all of what was making me sick - before that, I couldn't put it into words, I was simply miserable.

In my particular case it stemmed from spending my early childhood in a first world country and moving back to our third world country when I was 7. Dealing with the aggressiveness and irrationality of my native culture is something that left me unable to successfully integrate in that society. This in turn of course means I had few friends, trouble finding a girlfriend and difficulty entertaining myself. I had to find a way out. Moving out of course would be difficult. Third world salaries, family didn't support my decision to leave the country, no good way to insert myself in a first world society with security.

Fast forward 10 years: I managed to immigrate back into the first world through an education visa and convert it into a work visa. Have stable work with good pay, like-minded friendships, amazing girlfriend.

I still have "scars" from back then: some social awkwardness is still there, and sometimes I have blue days. But I know how to manage myself and work to identify and attend to what's bothering me.

The takeaway for me (not a doctor) is that some forms of depression manifest themselves in a healthy nervous system that's exposed to an adverse environment. We have some control over the environments we're in and that's where we should act.

Standard disclaimer - still look for a doctor. Therapy was enough for me, but it may be the case you needs drugs. Seek help. While you don't have to do this alone, you can take ownership and try to solve your problems, even though it might take years. It's worth fighting for.
With emacs, however, people tend to use tramp to edit files on a remote server as if they were local. So, there’s less need for actually using emacs on a server in the first place.
That's true, but 'null pointer exceptions' (which I suppose means expecting a Option<&T> to contain a &T when it is instead empty) are much rarer since nullability is made explicit.

Rust goals in life towards bugs are basically

- Isolate memory bugs to unsafe code which you rarely write.

- Make as many classes as bugs reasonably possible rarer by encoding as much as is reasonable in the type system and encouraging the programmer to think about all possible cases.

The first gets all the attention because it is the one you can make guarantees about, but the second is really just as important.
terminals unfortunately are a complete no-go for "all" Asian languages.

to my knowledge right now no terminal emulator properly handles

* cjk- specially so called double width chars

* Indic- dependant vowels

* west asia- rtl

that's the entire breadth of Asia for you who cannot use terminals if hey want to write a letter in their own language.
What kind of navigation are you relying on that could not possibly work faster on a terminal?

Horrible ascii graphs look horrible, but they are arguably more functional in that you can navigate them with your keyboard.
The Thermodynamics of Deep Learning
Why wouldn’t Strava clone Footpath? Does Footpath have a patent?
Rust is about zero cost abstraction. Bound checks can be disabled.
I don't get this post. Honestly.

Companies use this jargon of `breakthrough in the space`, it has been nonsense since Apple introduced FaceTime as a breakthrough in the space even though you had video chat for ages before that.
> The OP's point was that adding "ever" in the title means the question isn't just relevant to our current understanding of what is theoretically plausible but it also doesn't exclude some currently unknown theory that might be derived at a distant point in the future.

Or, somewhat more plausibly, some theory or technique that constitutes a minor subfield right now but could be the next big thing in another 20-30 years, or whenever someone just makes it really fast.
It's so much faster when you're not using the mouse. Move up to 'Transactions', then 'Customers', then 'Payments', then scroll down to which one you want to see.

Or you can do '5, 3, 12, <customer number>'

Try changing the work flow of the 60 year old lady in accounts payable who's been using that for the last 25 years, she will never bring you in brownies again.

Not to mention no fat web client interacting with a server in the cloud is as fast as interacting with the server in the basement of your own building.
Twitter to Acquire Medium?
> True, but I feel I would still feel shame in failing to keep my word

You can "keep your word", or not, to a person. When dealing with a large organization all that matters is what's in the contract. Shame doesn't factor into it because it can't be reciprocated. Corporations don't feel shame.
That’s 16%, not an order of magnitude.
The TLD choice is a missed opportunity. With that idea they should have at least used the ".rich"

More info: https://www.nic.rich/

Jokes aside, this business model is not going to see any kind of wide adoption.
In my experience with cloud - pushing 8 years now - it's a total fallacy that you can just run without admins. Every time I've come in to clean up a giant mess left by "devops" who were actually just devs who knew nothing about administration of servers I've found massive amounts of waste, duplication, zero optimizations and poorly operating systems that even a intermediate admin would have helped to mitigate. One place, just doing a bit of tuning and moving a few services on-prem resulted in a $200K/year savings.

Developers and Administrators have different priorities and I can count on one hand the number of true "DevOps" people I know - the rest are either decent admins and poor devs or decent devs but poor admins. The idea is nice but the reality isn't quite what its made out to be.
This is a bad article.

I've actually been spending some time recently trying to get to know about MMT because it seems like it is emerging as important in the mainstream - people like Ezra Klein have bought on people to discuss its merits and things like that. I have found it unfathomably difficult to understand what is unique or interesting about MMT in its understanding of the world. There seems to be one core conclusion - that the US can choose not to care about tax revenue. That seems to be an incredibly convenient conclusion so we really need to understand the mechanisms of why that must be true. That's where I fall down, I have yet to follow the argument as to why.

This article in particular seems to take joy in focusing on the unimportant parts of the article to which it's responding. The focus is to attack the author for their perceived attacks on the backgrounds of the people they're talking about.

I think one key argument in the original article that this one is attacking is: "If you print money to fund government too much you will get inflation. How does MMT say you solve that problem?"

There's a lot of emotive language in the response, but no answers. Only ridiculous attacks. The original article reads to me like a serious person posing serious questions about what the implications and mechanics of MMT are, and this response just doesn't address them.

I'm really only just getting into this subject right now, but MMT looks incredibly weak to me.
A provisional patent on the method would have been a really good thing to have in Footpath’s back pocket right now.

When you’re building functionality that’s whizz-bang cool and brand defining but that’s totally on display, when it’s one of those things that once you see it it becomes “obvious” that was the way to do it... a provisional patent could be the best ~$100 you ever spent.

IANAL, but provisional patents are double-edge swords. You have to file before an offer to sale or launching the functionality in your app, and you need to describe in enough detail what it is you are doing and how it is that you do it. You don’t have to translate this into patent-ese claims at this stage. But any claim you ultimately make in a full application claiming the priority date of the provisional must be fully supported by the provisional text, so it’s good to put everything you’ve thought of to that point in.

The other side the sword is that as soon as you file, a clock starts counting, you have 1 year from filing to make a full-blown patent application based on the provisional, or everything in the provisional then becomes theoretically unpatentable. Since full patent applications are expensive, it’s like a liability on your balance sheet for the next 12 months, because there will be pressure to spend the $10k+ to not “lose” the provisional.

One smaller benefit is that the priority date on the provisional is iron-clad protection against any patent on the same subject matter that is filed after that date.

I would not at all be surprised in a case like this to see Strava try to file some patents on the (copy-cat) feature they just launched. They might not go head-on, but try to patent back-end algorithms that they developed “independently” that probably line up closely with what Footpath already has — because it’s the natural way to approach the problem.
There are different reasons why a program can crash. Nullpointer exceptions are one of them. Out-of-memory situations are another. Rust protects you against the former, but not the latter. But at least in my experience I only encountered crashes when I disabled safety checks by calling .unwrap().
I got the impression that you're seeing into this too much, perhaps because you yourself have legitimate fears of failure and are turning the delivery guy into a symbol of that.

No one's life is alike. You don't know what life circumstances brought the guy from chemistry degree to delivering stuff. They could haeve been in his control or not.

What you saw was a person at a single point in time. Whatever your takeaway was, doesn't define who he is or what his life will be like forever.
Seems they reverse engineered it more than copy it.
> I would guess that io2d::refresh_style::as_fast_as_possible means as opposed to Vsync. Vsync times drawing or at least buffer swapping so that you don't get video artifacts due to the monitor reading say half of one frame and half of another. Vsync is not as fast as possible assuming you can render faster than 60 fps on a typical monitor.

That'd be a reasonable theory except it's not how any of this works anymore. Unless you are exclusive fullscreen it's not possible to get tearing on any modern compositor. Window's DWM, Android's SurfaceFlinger, Linux's Wayland, etc... on all of those you're drawing to an offscreen surface, and when you flip it doesn't go directly to the display it goes to the compositor. You're basically always vsync'd by the compositor. So for a windowed application what you really want is more like Android's Choreographer, or JavaScript's requestAnimationFrame - a callback that just says "hey if you want you could redraw now" for rate limiting purposes more than anything else.

And even if you are exclusive fullscreen there's things like adaptive vsync or even just choosing an alternate refresh rate.

> Also, who says the game will control the loop? In Javascript (requestAnimationFrame) and many other frameworks, that's not true.

requestAnimationFrame is simply a callback and entirely optional. That'd be backpressure control more than anything else, and you'd still have things like input intermixed with it.

Also C++ has threads, so discussing games or loops in JavaScript vs. C++ doesn't really apply in the same ways.
What argument? That Strava's employees examined a competitor's app? A lot of apps are in trouble if this is considered bad behavior.

Strava didn't steal any code. They copied a feature's presentation and UX, right? I'm sure Snapchat re: Instagram would be highly interested if there was a legal or even moral issue here, especially when there's no patent protection.
If you're charging 30% then donors and the projects they support are better off leaving you out of it and just interacting directly with each other as you don't appear to be providing any significant value to either side.
I feel most people that have used a command line workflow that need a GUI for debugging GDB's TUI is generally adequate even with large debugging projects. It's not a perfect 1:1 to the magic that Visual Studio gives you, but it is useful even with very large projects. Then again people who are terminal oriented usually use/look for other styles of debugging compared to people who have a solid IDE where the debugger just has more leverage. There's plenty of projects where all you are going to get from the field is a coredump, so building other methods to triage problems is more important: for instance a reliable replay system to rerun a trapped issue in a test environment.

If you are from gamedev land though everything is rigged around working with Visual Studio, so the debugging strategies/workflow I feel are more related to that than anything else. You also (generally) are debugging relatively locally to the problem as opposed to continents away. GDB and TUI stuff is wonderful if you are 6+ timezones away from the problem.
100K/year average. Consider they are not all highly paid engineers, Minnesota is like 1/3rd the cost of the bay area, a lot of it was outsourced overseas where they're even cheaper.
Snapping a rough/imprecise path onto a road system is not novel. The same type of algorithms are already used by all major mapping apps during rerouting and to correct for GPS inaccuracy during route transit.

Sigma also has this feature in one of their GPS units: http://disq.us/p/202igai
Performance comparison of Go, C++, and Java for biological sequencing tool
Love this story. How much did you charge for changing those two numbers?
So true. It’s hard to believe that their new control panels since Win 8 still lack features of the old ones.