skysight-inc/HackerNews huggingface dataset:
>On another note, checks charge 0% commission: to pay someone $5, you need $5.

I sometimes lead weekend trips for an outdoor organization and for quite a while even after various direct electronic payment arrangements became available, most leaders stuck with checks because there tended to be fees associated with other types of transactions.

I assume dealing with check fraud has become pretty bulletproof. I bought a car for "cash" last summer and I surprised I could just write a check for the post-deposit balance when I picked up the car. I've always had to go to my bank for a cashier's check in the past.
Since you're asking for 'downvote comments': UI themeing had already been solved decades ago, there's absolutely no need to bring AI into play for a solution to a problem that doesn't exist in the first place - on the other hand I get the impression that this is the one thing that AI is really good at ;)

But back to the topic: The reason why UIs are no longer themeable has zero technical reason, instead it's a cultural problem (the introduction of artificial 'fashion cycles' into UI design for no other reason than justifying the existence of a 'UI designer' job role.
You know that conquering territory on earth was profitable for the winners, right? There’s no profit on Mars.
Spring is a strange example. It’s main selling point is you’re not reinventing the wheel and, instead, building on well tested and operational work already done.
America is overwhelmed with illegal immigration so there are zero resources left to help with legal immigration.
most developers are not senselessly seeking complexity
It's not the users who would recompile the world though, but the OS vendors. And really in 2022 with a threadripper, rebuilding the world is a matter of hours: my 2018 laptop can build a complete yocto environment from scratch, from GCC down to a Qt GUI running on X11 or wayland in 8-ish hours IIRC and is waaay slower than a TR, so really there's no excuse to not rebuild.

Previous ABI would still be provided for running proprietary software on Linux just like you can still install libstdc++5. On windows apps ship the c++ runtime along with them so nothing changes for old apps. MacOS users are used to compatibility breaking every 3/4 years and went through actual architecture changes once every decade so obviously changing c++ abi is minor in comparison
tailwind is the best utility css library to use with React, you can make components with Angular, React became more popular than Angular because it didn't introduce new concepts like dependency injection and stuck closer to ES6 standards
Consider how desktop apps have basically disappeared. They're all in the browser now.

Also, ask yourself what the difference in UX is between serving templates vs. something like React. Are you not getting something in return?

There may be some artificial inflation but think about websites from 10 years ago.
Same for exceptions really. Exceptions don't give any guarantee of non-erroneous state. The guarantees that you're talking about actually come from how construction and deconstruction work in C++ (note how it plays with early returns just fine, no exceptions needed). And these construction semantics can be implemented with variant types as well, it's completely unrelated.
> My surprise is that Android is the "other one" and not Windows Phone.

I'm not. Microsoft, with WP, copied the weak things from iOS (like being locked down, but also with very poor walled garden; single platform, Snapdragon reference design only), but not the strong ones. Android did it the other way, so I'm not surprised at all.
It's a combination of:

- Fast Fashion for web sites. Users are kinda like kids in a toy store, always jumping to the newest & coolest & shiniest things. OR - at least the suits making the calls are far-too-often convinced that they need the newest & coolest & shiniest web site, to compete for users.

- One-upmanship among young male web developers, who always want to be working with newer / cooler / yet-more-complex technology than the next guy. And how very convenient that newer, cooler, and more complex technology tends to pay far better, whether it's needed or not.
Internet explorer made life a nightmare. had to have if statements around most everything.

Corporate was very slow to roll out new versions. So we could get to be years behind. Things like custom Active-x apps required specific versions.
For a perspective, I'm not American, and I don't feel comfortable giving my bank details to random people.

I can also get checks with dates in the future, and know that I will collect the money (this way or another). If someone promises you a future money transfer, you can't be sure that they will actually deliver the way you can when you have their check in hand.
I agree the premise of these sorts of pieces is very flawed, and I'm surprised in these discussions the assumptions are put forth so matter-of-factly.

Grades don't necessarily exist to maximize some spread and produce a nice normal distribution. They could be constructed that way, but the way they tend to be used is in communicating level of mastery with material, and if a course is well-constructed, the instructor teaches well, and the students are engaged and learning, they should generally mostly get "good grades."

The weird thing is, how do you know that Harvard students aren't basically all understanding the material in their courses well? Wouldn't you expect that?

Think about it another way. Let's say universities tried hard to improve their educational effectiveness over decades, and were successful at it. More and more students were understanding the material in courses better. Why shouldn't that be reflected in improved grades?

At some level as you point out what really matters is whether or not a student basically grasped the material well enough, and the grading system in some ways punishes risk taking by grappling with difficult material.

I was a professor for many years, and there were certain universities that were known to have extremely low GPAs (yes this still happens), so we had to factor that into graduate admissions decisions. It did nothing but hurt applicants. Those students had the benefit of coming from schools that were well-known enough to be on people's radars, and for word-of-mouth to afford admissions committees knowing about grading practices. Students from smaller schools wouldn't be so lucky.

On the other hand, GPA might be more predictive of outcomes than standardized tests (https://news.uchicago.edu/story/test-scores-dont-stack-gpas-...) so this discussion might be moot. It doesn't mean that something couldn't be improved about grading but it's odd to level these kinds of critiques at GPA if it's outperforming the biggest alternative available).
Okay, but what happens if your device(s) have been compromised, and a payment is misdirected?

From the perspective of suffering large bureaucracies, procedures with obvious possibilities of failure have an advantage in that the bureaucracy will have to entertain the idea that something exceptional happened, rather than simply running your edge case under their steam roller.

I admit this might be a very USian view, as we have extremely unaccountable bureaucracies here.
I disagree with the premise, things have gotten a lot simpler.

I think you need to make distinction between website and web application. The latter came later and is by definition a lot more complex, I assume this is mainly where the premise originates from.

But having gone through building websites with frames, tables, png's for box shadows and border radius, jQuery and php based web apps, and having spend many days making my grunt/gulp/webpack config work and supporting IE, I can with great certainty say things have never been easier than they are now.

Now, is it necessary [to build webapps]; Yes. Usability expectations have gone up, the level of details and polishing has gone up, more interactivity, and more sophisticated visual elements. Webapp now do things native applications could not do back in the day.
> You don't just get trust for free, you have to build it by creating moments like this where people can demonstrate vulnerability around each other

Not every company is an ideal organization where demonstrating vulnerability is going to lead to a positive outcome. Fast growing orgs are often stuck with bad actors because hiring a replacement is difficult, in some cases virtually impossible. You will be stuck in a political game before you are even aware of it and forced to work with people who hate you because you worked for a FAANG or whatever tickles them.
TWenty years ago windows development was a lot simpler than modern browser applications. Fire up visual studio and create a new winforms project.

You could literally drag and drop your way to a modest application with only minimal programming 'under the hood' for the business logic.

I still don't think anything has surpassed the usability of winforms for a developer just wanting to get something done.
...or developers think that. Or they pretend customers will care because they really want to play with their new framework.

Nowadays everything is a single page app, and for 90% of website/web apps it would be better (and orders of magnitude simpler) with good old server rendering. It would also be much faster.
Not sure why you are down voted. Let's hope your hn account wont be closed as well now "they" know what you did.
I’m fairly confident executable text as well the other functionality of current smalltalk systems can be implemented within a modern IDE framework. What needs updating are the UI components, views, layout, etc. For example, I can envision a left hand tree component for the display of packages/classes/protocols/methods the same way it’s done for for almost every other language.

Could the modern IDE paradigm be approximated within current Smalltalks? Probably, but pulling that off in Squeak or Pharo seems like the wrong approach. Also, deployment of server side applications is more cumbersome in Squeak or Pharo than with GNU Smalltalk.
This. While engaging in flame wars about React I have noticed that all of them start with a peculiar definition of done that, lo and behold, necessitates not only React but whatever feature if the month they are busy ductaping to it.

What we need is an honest conversation about what USERS think about spa apps, flat design, etc while holding very obviously interested parties from skewing the narratiwe.
This reads needlessly aggressive, and the accompanied downvotes seem unjustified.

In addition to the other studies published by Wiley, I have two more:

https://journals.sagepub.com/doi/10.1177/0956797620924051

https://journals.sagepub.com/doi/10.1177/0956797617736887
A lot of junior webdevs, iOS app devs and designers were buying Macs to run testing/staging envs, and they have a lot of leverages, so MS had to do what they did.
1. Is Changpeng “CZ” Zhao known to be someone who believes in "Code is law"? I know that some in the crypto community (specifically ethereum/difi) believes this, but this isn't as much of a gotcha you think it is because crypto isn't a monolith, and therefore there can be apparent contradictions from people within the crypto community.

2. On a more fundamental level, I don't see how this is inconsistent with "code is law". After all, if the attacker willingly transferred his stolen funds to a third party, then in the eyes of the network he legitimately gave up control of it[1], just like luke legitimately gave up control of his coins when his wallet was hacked. Live by the sword, die by the sword.

[1] if you want to make it kosher in the eyes of the law, you could even sneak a clause in the ToS that says you have the right to freeze whatever funds you want.
They won’t. Space problems are not earth problems.
> "they installed a proxy on my IP"

This doesn't make sense.

> "they sim-swapped me to intercept the one-time password".

You would notice by losing phone connectivity... so you would know you're compromised before you try to make a transaction.

Being 2FA, the attacker still needs to know the account user/password...

Then there's hardware 2fa for a lot of banks that don't do sms... good luck with that.

Or they use bank app in phone as 2fa. Which should run securely in enclaves.

Even if they have all of the above, you just file a police report for fraud and bank will claw back funds and reinstate you, same as for checks.
Indeed. It wasn't justification any more than Root Cause Analysis is making excuses for a systems failure.
People wanted applications and app-like behaviour in the browser. And browsers are uniquely uneqipped to deal with that:

- the core if the web has been, is, and will forever remain a system of displaying static text with a couple of images. You as much as look at it funny, and it needs to re-layout and re-render the entire screen

- there's no standard library to speak of

- there are no standard widgets and controls to speak of (https://open-ui.org/ is twenty years too late)

- there are no easily accessible ways of handling state

- almost every single API that the web provides is either underngineered, or overengineered, or badly designed, or all of them together

- the web rarely provides a comprehensive and/or a generic solution or an API. It's a hodgepodge of one-off hacks often needed to cover deficiences in other hodgepodge hacks

So, to make the web even remotely app-like, you need to solve for all these issues, and that's before you even start writing a single line of app logic.

And on top of that you have language evolution and people wanting to use features of tomorrow today.
Nobody reads them, is it because they aren't useful? Maintaining wikis is a culture thing. If most of your employees don't use the wiki it's basically useless since it'll be falling out of date.
Most of the state of application used to live on the backend but now that has transition to the frontend. Dealing with the state of application is difficult because of edgecases and side effects, React can handle many different domains mobile, tv, and website. Of course development will be more complex with more target domains.
..... Yeah.... That makes sense to me?
The main reason is easy “to plug and play” various tools, i.e react, websockets, graphql, webpack etc. That’s not related to frontend only, but kubernetes devops are also crying from complexity.
Here's what I have:

- Standing desk

- Two 24" monitors, each on single Humanscale monitor arms (bought used on eBay, at a significant discount). I switched from dual arms to single because the latter means that I can move one monitor without affecting the other.

- Tenkeyless mechanical keyboard (MX silent red switches)

- 60% mech keyboard (MX brown switches)

- Vertical Logitech mouse on a mousepad (that looks like a mini carpet)

- Work laptop

- Microphone on a Rode arm (bought used on eBay) that's fixed onto a wall shelf

- Custom-built PC in an ATX Mid Tower

- HDMI switch that lets me use my main monitor with my work laptop and my PC

- USB switch that lets me do the same with my keyboard and mouse

- A collection of mechanical pencils in a ceramic sugar skull
Why are there so many tech layoffs, and why should we be worried?
Even if it ends up the same, it will differ from the ethical framework of NYC cosmopolitans. Having more diversity of thought would be a good outcome.
It's the worst EV on the market. It's only a compliance car, not something they expect anyone to drive.

Toyota/Subaru aren't much better. Japanese carmakers seem to hope that BEVs are only a fad.
The browser is powerful enough now that one could replicate this if one wanted to. I don’t think it’s the pinnacle of software development, but it had some advantages.
Nothing surpassed Delphi from early 2000s. Not even WinForms.
But developing a windows program is simpler.
What's Real?
I came across this article after Googling the Jefferson quote cited at the beginning of the article: “How much pain have cost us the evils which have never happened.” I heard that quote this morning in a podcast interview with Ken Burns and it hit real close. I thought it might be helpful to any other worriers out there as we start the new year.
Yes, and moving to the EU was like moving forward 20 years. The IBAN system is fantastic! The seller gives you their IBAN number, and you tell your bank to send money to that number. It happens instantly and for 0% commission. There are no routing number/account numbers. (Granted, I never had to deal with fraud so I'm not sure how that goes. I doubt that credit card style charge backs are possible.) It's also interesting that in some parts of Europe (esp Germany) cash is still the normal way of paying, even for large amounts.
I've come to believe that a deep childhood wound (parental divorce, neglect, abuse, or being adopted, etc.) predisposes one to become a narcissist when combined with the message that you are special, different from others, etc.

You just described my childhood.
How would you incentivize nodes long-term without a reward/token system?
Same for MVC/MVVM and Co specifically on mobile. These things were created to teach beginners a few important concepts, mainly separation of concerns. MVC/MVVM work well on toy sample projects with 2-3 pages but can ruin a larger project. Somehow wherever I'm seeing MVVM applied there's also messy, buggy, impenetrable code around it. I don't think it's a coincidence.
> these apps are a minority.

I disagree with this. Almost all front-end projects I've worked on in the last 10 years or so have had some requirement that made pulling in react a better choice than trying to push back on business and/or get buy in to do everything server side. Providing users the kind of tighter feedback loops for their workflows is only possible with JavaScript.
As others have linked already: https://www.reddit.com/r/Buttcoin/comments/4936kw/lukejr_is_...

Plenty of dumb things to chose from that they allegedly said.
It should run just fine on wine on Linux, according to the reports: https://appdb.winehq.org/objectManager.php?sClass=applicatio...
There's a lot of negativity and pessimism in general on HN these days. Changing times, changing demographics. I took a break from it, returned today, and will be continuing my break from HN. Whilst the aggregated content itself is interesting, the opinions are fluffy. E-peen points really do encourage a Reddit-like attitude in the comments.
Web apps used to be just html and forms so no the complexity has skyrocketed.
I've done frontend since IE6 was the major browser. Back then most of the time was spent using hacks to work around the limitations. No rounded corners, no opacity, no grid, etc. As it got easier, with better adoption of the web standards and better tooling, frontend-devs were able to do more.
But I feel as REST and GraphQL got more adopted a lot of the complexity moved from the backend to the frontend.
The frontend part is easy these days, but working with the backend is the hardest part of being a frontend developer.
Can confirm. I love winforms. Convinced that even the most hardcore Unix devs are missing out on the sheer joy of being able to double-click on a form you just dropped into an editor and seeing it automatically add an event handler for the common case of whatever type of UI component it is. (Buttons are onclick, inputs are ontextchange, etc.)
Well, they can still be right but lose on that trade because of delta decay.
> As someone much more experienced in other languages like Python and Swift, my biggest surprise when using C++ is that the language standard and the compiler are two different things.

Yes, that's because C++ is a formally standardized language, and Python and Swift are not. C++ is an ISO standard, and it is published in text form. You are free to create your own compiler, and if it works according to the rules written in the official standard, you may call it a standard-conforming compiler. There are of course other languages which are also officially standardized like this (does not have to be ISO), for instance Common Lisp, Scheme and of course Javascript (ECMA).
If a language is defined by a reference implementation, then this is an informal way of standardizing your language, and if you want to create your own compiler/interpreter for such a language, you have to carefully evaluate what the reference implementation does.

> I understand it has to do with breaking ABI, but what exactly does this imply?

Very roughly, it means that you cannot link object code with the current ABI with object code that was generated by older compilers with the old ABI (well, it's usually worse: you can link just fine, but your program might or might not crash). This is not unprecedented in C++, we had this when switching from gcc4 to gcc5, it was definitely pretty painful and I'd rather not have this again.
I'll propose a couple more:

1. If someone mentions having just returned from country X, do not take this as an invitation to launch into extended monologue on your trip to country Y of ten years ago.

2. Do not ask people what they "do" -- to a shift worker of low-level service jobs, it yanks the mind's attention back to recent humiliations inflicted by rude customers or oppressive managers. Similarly any other question that might be heard as an attempt to gauge social status.

You will see these faux pas a lot -- the trick is to not fall into them yourself.
It’s like QE being a tax on everyone, and tightening being a donation to everyone.
To be fair most front-end projects have abandoned redux now. It was for sure boilerplate hell.
ShowGPT is a user library of clever and useful prompts for ChatGPT
All the crypto mining dying off should free up a lot of grid resources for EVs.

I've heard the "grid can't handle all EVs" statement, but have not seen anything backing up the claim.

I believe the grid can in fact handle EVs becoming prevalent. We might need more power generation, which could be new plants, and/or residential solar.

Baring some kind of crazy legislation requiring ICE vehicles to be crushed or permanently parked, we are decades away from a scenario where pure EVs are the dominant vehicle type on the road. There are just too many serviceable ICE vehicles in play to expect them to really go away in the next quarter century or so. That allows plenty of time for anything the current power generation and distribution infrastructure lacks to be adequately addressed.
I had no idea it even had that feature. File revision ought to a basic OS function and basic computer skill. One drive and Dropbox kind of give it to you. MacOS does it (you can save named revisions in addition to Time Machine working pretty well) but it’s not become a well-known feature for some reason. On the other hand these features may cause pain if they aren’t something that will survive copy operations, OS updates etc.
Man, are you kidding me or you are a troll or a CIA ops?

Doroshevich died in 1922, 7 years before Stalin took power!

Sakhalin was written 20 years before the October Revolution! What the fuck are you talking about?

You know what doesnt make any sense? To quote works of fiction written by novelists 20 years before the Russian Revolution to argue against Stalin.

This is the life expectancy in Russia since 1845: https://www.statista.com/statistics/1041395/life-expectancy-...

You can see that Stalin was directly responsible for increasing life expectancy from 37 years (in 1930) to 58 (in 1955). That's 20 more years! And the communist policies almost doubled life expectancy until it started to stagnate in the 60s.
Also, part Stalin, part Lenin were responsibly for erradicating illiteracy from the Soviet Union, read about the Likbez.

Those are facts, not some works of fiction written by some dude 20 years before the russian revolution.
Via https://old.reddit.com/r/InternetIsBeautiful/comments/101brq...