skysight-inc/HackerNews huggingface dataset:
Love this question because it puts the issue in very stark relief.

No, fast food workers shouldn't be tipped. No one "should" be tipped. If people are paid a living wage then scrabbling for tips becomes obsolete and tipping leaves the realm of "should" and progresses closer to its Platonic ideal of being a purely voluntary act used to express exceptional appreciation for a job well done.
Would you say this is an honest statement, or an intentionally misleading one?

Follow up question - with thousands of hours of footage of the events, has anybody been charged with any murders?

Last question, why would you post an intentionally misleading statement like that, do you think it helps your argument or hurts it?
Maybe controversial opinion, hold onto your mojitos: if board members, executives and founders can buy individual stocks, then congresspeople probably should be able to as well.
Amazon will get its mojo back. Death Star will move in 2022, here is why
FutureLaw 2021: opening keynote by Alan Kay
> Roads are the most commons example of induced demand. Adding new roads rarely decreases travel times because new roads encourage more people to drive which leads to more traffic that soaks up any benefit the new roads added.

The problem with "induced demand" is that it's misnamed. It's really suppressed demand.

Suppose you have a congested road. It has two lanes and currently has enough traffic to require three lanes. So you add a third lane. Then you turn around and it's congested again.

Because the congestion suppresses demand. The third lane relieved some of the congestion which increased use. To satisfy the demand that exists when there isn't any congestion, you would need four lanes.

But not necessarily five, because once the congestion is gone, adding more lanes doesn't make it any more gone. If you built a twenty lane road there, traffic to fill it wouldn't just magically appear. (China has done the experiment.)

This is important because it applies to anything else you want to use to relieve the congestion. "Don't build more roads, that's induced demand. The only solution is more mass transit." But if you build the mass transit and it removes one lane worth of traffic from the road, that's the same result as adding the third lane. Which isn't enough for the same reason -- the reduction in congestion increases use of the road. Because the demand isn't being induced by a wider road, it's being suppressed by the existing congestion.

The internet speeds are a great example. In the dial up days, the low speed heavily suppressed demand. Your connection was pretty much maxed out whenever you were using it. Now connections are 1000 times faster or more and we use what, 20 times more bandwidth? Maybe 100 times? The speed increases outpaced the usage increases. It's possible to do that.
That would be ideal, but there are huge differences between the window implementations on different platforms.

One really obvious example (maybe no longer current - it's been a while since I spent any time on Windows) is that OS X windows are responsive even without focus. So you can scroll around background windows just by hovering without having to click first. Windows doesn't support this.

The bigger problem is that the data structures for menus, chrome, and the rest are completely different. An OS X menu is nothing like a Windows menu is nothing like a Linux menu.

There are systems like Tcl/Tk and Qt which act as middleware between GUI descriptions and specific OS bindings, and they kind of work. But they force devs to learn a separate intermediate language and (IMO) they look crude compared to real native apps.

Of course there are also business reasons why GUI convergence won't happen.
On Android, can WhatsApp do SMS? At least previously any app could interface with SMS on Android.

Few countries (only the US? Canada?) actually have any real social usage of SMS at this point. That’s becoming increasingly the case in the US as well, Apple/iMessage aside. Everyone else has picked an app instead (usually given an effectively local monopoly to an every changing array of owners over the last 20 years). That’s true even on Android without this SMS gatekeeping status that you speak of. Given the world is majority android, and the lack of SMS/RCS leading to any kind of decentralization, your argument doesn’t seem to have much merit that opening up iMessage would usher in a new decentralized era.
Yep, and the highest data rates are only really possible on the best processes (12nm, 7nm, 5nm) , which is a fun chunk of change to spend for a tape out.
Actually, it was green.

I am always surprised whenever Mozilla posts this, that no one seems to go straight to the horse’s mouth. So I will:

https://www.w3.org/People/Berners-Lee/FAQ.html

Rendition of links

Q: I'm a student of visual communications and asked myself why links are blue. I found some answers that might be, for example blue is a color of learning, but I'm not sure what is right. Is there any reason, why links are colored blue ?

A: There is no reason why one should use color, or blue, to signify links: it is just a default. I think the first WWW client (WorldWideWeb I wrote for the NeXT) used just underline to represent link, as it was a spare emphasis form which isn't used much in real documents. Blue came in as browsers went color - I don't remember which was the first to use blue. You can change the defaults in most browsers, and certainly in HTML documents, and of course with CSS style sheets. There are many examples of style sheets which use different colors.

My guess is that blue is the darkest color and so threatens the legibility least. I used green whenever I could in the early WWW design, for nature and because it is supposed to be relaxing. Robert Cailliau made the WWW icon in many colors but chose green as he had always seen W in his head as green.

One of the nicest link renditions was Dave Raggett's "Arena" browser which had a textured parchment background and embossed out the words of the link with a square apparently raised area.*
Internazionale is actually the best newspaper in italy. The opinionists are very smart too.
The thing I really hate are 18% service charges tacked onto the bill and...a note that you should still tip in spite of the service charge. I mean, what?
You bought a device and want every one else to make software for their devices to make your device work the way you want it to.

I don't think that's the way the world is.
Now if only PCIe had woken up two years earlier and spent a bit more time on development… then PCIe 4 would be the equivalent to this new PCIe 6 standard.
The most important was the horse collar, which was like turbocharging a tractor. The use of horses to farm also exemplified the class changes. Horses didnt die of plague. Thier owners sure did. So the horse became cheaper and lesser classes of people put them to uses that previously would have been benieth thier dignity.
Invest into your own super wonderful alternative and they'll crumble at mere sight of your engineering superiority.

Or not.
Just to be clear, the research article has no such assumption. This is the PR person at Stanford interpreting things on their own.
You and I work on very different kinds of projects. I find myself fidgeting and squinting at the database far more when it fails to enforce a schema or provide ACID transactions.
You have a highly specific definition of good enough that doesn't match my experience with it's usage. Every time I have discussed whether something is "good enough", the discussion centers on what the relevant risks, needs and priorities are. Indeed, adherence to relevant standards should be part of the "is it good enough" discussion, but following standards alone doesn't absolve you as a devolper from assessing the current contextual needs and risks.

Indeed, blind adherence to standards is bad as standards are not perfect and are designed to fit a general use case. You need your developers/engineers to think about the full context and asses whether their design will hold up under real life conditions and not just those that were prevalent when the standards were created.
>I’m just thankful I can develop my own projects without the insanity

What a blessing indeed.. I want to retire from it too, but I've got a long way to go yet to keep making rent.
I’m not sure about C++ in particular, but in general a lambda can capture a lexically scoped value and expects to still be able to access it even after the stack frame it got allocated in is popped. GC is the most straightforward way to keep that from leaking.

On a tangential note, the amount of Greenspunning C++ has done over the last two decades is truly impressive. There sure is a lot of syntactic noise though.
Was this supposed to be a rallying cry, or a grumpy rant? I'm getting a mixed message.
Worse than that, they hijack the whole contact. I have an iPad and an Android phone. Whenever someone with an iPhone would send me a message it would always go to my iPad via iMessage. I think the sender could change it on their end to use SMS for my messages, but you have to explain it to every iPhone using friend and they all tell you it “just works” with iPhones. Lol.

Eventually I had to disable iMessage.
I perhaps used the wrong word, smart contract explainer would be better

A lot of times ( i think) the source is available but people don't trust it and don't understand it.
Common Lisp lets you do that, but Clojure doesn't - I don't know about Ruby, but I expect not. That said, you have the wrong mental model. You don't run the whole program and set breakpoints. Instead you directly interact with your program-space. Imagine you have a function that retrieves something from an API. So you execute that function and see what it returns. You change that data around a little to fit your usecase, and then hand it off to the function that acts on the API result. That will produce more data; maybe this data is wrong, so you change the function, recompile it and load it into the program space, and try again with the same data you just changed (which is still right there in the variable you defined). Does that make it clearer?
I was wondering about that too. Yeah that's probably it. Maybe carpal tunnel has made it hard for them to type to fix the typos?
> So no principled justification to tip in those places, unless you like to tip for every service for some reason.

While they may make minimum wage, in this day and age, minimum wage is well below what you might make otherwise at a non-tipping establishment. Tipping is still expected at restaurants in Washington state, and is still the main source of income for most servers (the minimum wage they earn is less than the tips they receive, and if it weren't for tips, they wouldn't bother doing the job for minimum wage).

I'm against the requirement to tip as a way of doing business, but will do it as long as it is expected. Ideally, we'd do things more like Europe or Japan.
Can you pinpoint these "MANY unfounded assumptions" in the research paper? I read the paper but I don't see where the author is making these assumptions.
I feel comfortable asserting you've never not used a complex web application, even for your personal non-commercial projects made for fun. The fact that his website (and other projects) is in HTML and doesn't need to be executed is a confirmation of the article ideas not some deficit.

You can justify what you do with JS for money however you want but businesses do it that way because managers decided it's cheapest way for many people to collaborate, not because it's the best way for end users, security, or longevity.
> I would not normally be quite so much of a jerk about the numerous syntax errors, except that this ends with a suggestion that people, you know, pay for this writing. I don't expect perfection (God knows I make tpyos all the time), but the closing paragraph starts with a sentence that literally has no verb.

Are you really bashing the author for imperfect English? The about page clearly mentions that they are not a native speaker of the language, and even apologises for any imperfections in their writing as a result thereof [1].

I strongly agree with your parent comment that attacking the author for presenting their strong views in an area is unnecessary. Make arguments against what they wrote, not who they are.

A little kindness also goes a long way. What the hell is this obsession with hammering everyone down with unwarranted negativity on this forum.

[1] https://unixsheikh.com/about.html
Okay, but there is no iMessage app, it is a protocol available to Messages users. Messages is the default SMS app and it defaults to using SMS. If a user ops in to iMessage, they get E2E and the other iMessage goodies. If they don't opt in, it does SMS and MMS. Even opted in, it does SMS and MMS to non iMessage users. So, the user has the choice to participate in iMessage the protocol or stick with SMS. Both options are available within the default SMS app.

The question here is whether Apple should be forced to implement RCS. They aren't stopping anyone from communicating since SMS and MMS are available. I suspect if RCS gains enough traction, Apple might add that capability for non iMessage users. I don't know that of course, but I wouldn't be surprised. iMessage still has many advantages over RCS for in-ecosystem users so it wouldn't harm them to add it. Time will tell I guess.
It is a trade off.
How much did they really gain by using ?.

A year ago I helped a small company with some issues. One was that some people working with them had some problems using their app with older phones.
After some investigation it turned out that I just had to replace "let " with "var " on a few lines of javascript code.

I used an an Iphone 4S for the testing and the browser could not be updated.

I you make something that could work on older devices and it is not too much trouble, you should make it work on those devices.

I have a drawer full of old devices that I use for all kinds of things (besides testing) where it is not a big deal that the software cannot be updated.

I do have an old chromebook. It runs Debian sid and has updated browsers.
We need a new Pidgin https://www.pidgin.im/ :(

There were a few brief wonderful years when I had AIM, FB Messenger, GChat, and a few lesser known protocols all in different tabs in the same window.

It's not like they all needed different interfaces; same data, different wire-noise...
Indeed - my self hosted email now gets the majority of its spam from (not forged, DKIM-validated) @gmail.com addresses. I'm on the verge of blocking everything @gmail.com except for known contacts.
See his next tweet: https://twitter.com/RonAmadeo/status/1480679860381138947

I think he's right: the big problem I have with SMS is that it's run by the carriers, who are terrible at non-phone infrastructure — that's how you get SMS delivery latency ranging from seconds to days, completely opaque to the user, and new features are a long, slow grind. RCS preserves that model going forward.
Senders and Receivers is the next big thing Eric is delivering to C++, stay tuned.
iMessage seems like the WeChat of America. It has a ton of integrations but if you exist in any other part of the world, it really doesn't make any sense to use it, since maybe 1 out of 5 people will be reachable.

SMS is like a spam graveyard where 2FA codes and other regulatory compliance related stuff shows up. SMS is primarily texts from my bank and spammers. Most folks in the rest of the world are using WhatsApp, with the occasional country where Telegram is more popualr.

Messaging with a layer of rich features for billions seems like a hard problem. I'm not sure what iMessage is built on, but WhatsApp is using customized erlang/ejabberd and Telegram is its own golang MTProto stack. Each probably handle millions of connections on FreeBSD or something I suspect.
Yes, in my game during December all NPCs spawn with christmas hats.
>States like NY, NJ, CA and others have mandatory reporting requirements, so test results get returned to the county or state DOH and are verifiable.

Those states have no rapid tests? Nobody in those states can buy a test at CVS and take it at home?
As for the arguments you demand, I think it would be more efficient for everyone if you -- individual you! -- took up the mantle and accessed (for yourself!) the copious amounts of research and analysis present across the known universe, instead of repeating exactly the mistake that GP makes in assuming this conversation is not happening everywhere all of the time.
SMS would be terrible as a new solution now. It is still useable because it works in any situation where you get a 2G signal, but it is mostly used as a fallback. And around here SMSes are free and unlimited in €2/month plans (data is the new cash cow).
> Long compile times disrupt flow, and it requires great ongoing mental effort to work around slow compilation.

We once reimplemented automake in KDE land (into a tool 'unsermake' by Stephan Kulow), for a few reasons but foremost among them was that it reduced compile times, sometimes drastically.
From the FAQ: https://news.ycombinator.com/newsfaq.html

> Are reposts ok?

> If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates.

It's not clear what "significant attention" means- I use my own rule that is something like 20 upvotes or 20 coments (or 20 upvotes+comments). It's not an oficial rule and it's not a very clear rule. But with 144 points and 46 comments, I guess the mods will agree it's "significant attention".

My recommendation is to not repost it, but make some interesting blog post aout an interesting problem you solved in he project. It's important that it's interesting, not some silly topic used as an excuse to link your project.

If you meet an old technical friend, and you must tell your friend an interesting anecdote about your project, what would you tell?
My biggest issue about tipping is the arbitrariness of it. Why do delivery people get tips (pizza, waiter, porter, taxi, etc), yet other low income workers don't? If you worked low income jobs without tips, the entitlement of the tipping workers is off putting. Also this is an international audience that may have tips, but not the different minimum wages for tipped workers that is unique to the USA. Within the world of low income workers, there becomes a split of the untipped and tipped, and the tipped are basically the higher paid ones, which feels hypocritical when they complain about it while your sitting there without it.

Then you get into the naked racism, ageism and sexism that tipping exposes in who gets tips and what the tipping professions think of those various groups too.

Move on to later in life when you have better jobs, and the entitlement of the tipping classes and tipping alumni makes you eye roll inside because you never had that favor.
Like the Radio 4 Doomsday protocol?

https://www.express.co.uk/showbiz/tv-radio/1528497/bbc-radio...
Ah my mistake sorry.
I’m not sure I understand what the point of this is.

If I’m reading academic papers on a particular topic then I already know the notation the math is written in.

If I’m reading a paper outside of my field then I’m not really interested in the details of the equation but more of its application and what it means.
Yes! Also ease of printing means that even the local tennis club manages to produce a 10 page sign up form.

I think this is also caused by the incentives present: the form-designer is incentivised to make sure info isn't "missed". The wasted time from filling in a long form / filling in your name for the Nth time doesn't matter to the form-designer.
Hmm, many parking starved cities I've lived in tend to have permit systems in the especially bad areas that (1) only allow residents to acquire permits and (2) have ramping cost structures (like $0-$10/mo for the first permit per household, ramping to something really high like $100/mo for like the third).

It's also pretty common for apartment complexes to have a "loading only" spot in front of a building for deliveries and moving etc.

Also most cities tend to have restrictions for free street parking like "no more than 72hrs in a spot". Although I suspect this is to discourage RVs...
Tracker music in a nutshell.
github is a MITM, so not exactly.
Nobody Cares About Decentralization – They Just Want to Get Rich
I’m also not seeing U.S. Mask on that list. The thing I like about their KN95 style mask is that each one is individually packaged, unlike almost all the other masks I’ve seen.
Lambda GC doesn't matter if they're just syntactic sugar for plain old functions, which is how it is with G++.
FYI fxtentacle, people keep upvoting this comment- there seems to be enormous interest, it's already at +17.

Will be sad if we never hear from you.
Air conditioning, refrigerators
I thought you said this was a war on general purpose computing. Wouldn't the arbitrary group then be anyone who uses a computer?

I don't want to restate everything I said above (which you definitely need to reread before you even consider responding to me), I just want you to see that you are a walking meme and should take a moment to reassess.
> Even if everyone was running Windows on an corporate machine, it was still more difficult to deploy new code than it is today

Is that true? As someone who was also doing native Windows desktop applications back then (C# and VB in .net from 2006-2010), ClickOnce handled everything pretty reliably for Windows XP/Vista/Server (even with weird DLL requirements -- for example, I had to ship a QuickBooks Desktop API wrapper and propritary Epson drivers in our .net desktop app)

Yes, it's not quite as reliable as "go to my-app.com". But it was way more reliable than Electron's current self-updating (.net ClickOnce loaded in a tiny fraction of the time that Slack and Discord's Electron apps take to check for updates on every launch)
A Chronology of Personal Computers
I wonder how much of the land is going to become farmable now
There are ways to speed up compilation. It can be done in parallel, and you can get a lot of cores into a developer desktop these days. Plus you can get unlimited amounts of distributed cores in the cloud. Compilation can also be sped up with pre-compiled headers, which will soon be replaced with C++20 modules which will help compilation improve in the future as compilers improve their support for modules. With incremental compilation, you do not need recompile the whole project after every change. Linking in large statically linked binaries is a big bottleneck, but incremental linking is possible in some cases. You can also break your project into multiple shared libraries (DLLs) , and link dynamically at run-time for debugging. It can then be re-built with static linking for a release build. Continuous Integration systems can also help hide the latency of compilation from developers by continuously running build and test processes in the background on a cluster.
It's also possible to simply set the `$GIT_SSH` environment variable or `core.sshCommand` config option to an unencrypted shell like `rsh`
I just go down a percentage category if the tips are calculated post tax.
Teams moved to Edge instead of Electron. Your point still stands though. Not sure why they decided this was the way.

https://techcommunity.microsoft.com/t5/microsoft-teams/teams...
The answer is actually in the original Scott McCloud comic http://www.google.com/googlebooks/chrome/ . A few highlights are on page 17 (about V8 JS engine) and 36-37 (about Chrome in general)

Chrome/Chromium and its stack was designed to be easy to reuse and build upon. This may have been an explicit design goal because of the difficulties with reusing parts of Firefox and other software.