skysight-inc/HackerNews huggingface dataset:
> Perhaps, but going down that path means making a moral judgement about every activity someone undertakes. Fuel efficiency is at least fairly objective.

That's like the drunk searching for his keys under the streetlamp rather than where he dropped them. Does that mean it's somehow environmentally friendly to drive an 18-wheeler on a road trip rather than a motorbike, because the per-ton fuel efficiency is higher? The fair comparison to an RV trip is an equivalent vacation experience, and while we can argue about the details of what that means, it's certainly not just an equal tonnage.

> Whether someone should stay at home instead of travel in their RV, that is a moral thing. And I'm pretty sure that just about 0 people have an unassailable record of life choices.

Ideally I'd like to set a carbon tax at a level that fully covers the costs of repairing the damage, and take the moral element out of the equation - then we can just say that x litres of petrol costs y, and it's up to you whether that's worth it or not. But given that we don't have such a thing (and these people are presumably not offsetting), I'd say that you should at least make sure the fun you're getting out of something is proportional to your emissions; if you're doing something that's marginally fun but extremely polluting then I do think it's fair to judge you for that.
> I don't see how making router software open source for a company that is selling hardware is not a win.

There are several business tactics that are foreclosed by making the router software open source, mostly around price discrimination.

For example, you can't sell the same hardware for different prices with some hardware features turned off in the higher-volume cheaper SKU (which lets you apply greater efficiencies of scale to producing the hardware).

Of course, most companies that use price discrimination are only trying to maximize their profits, but it is worth noting that since hardware vendors that keep their software closed are able to pursue this tactic, it can leave hardware vendors with open software at somewhat of a disadvantage.
Ask HN: Do you wish Shopify accounts worked more like Uber or Airbnb?
The idea of Shopify is great, but I find it really frustrating that I have to re-enter all my details (address, email, phone number, etc.) for every shop. Why can't we just have one Shopify account and be able to log in with that Shopify account on any seller's website that is using Shopify? Why do we have to create separate accounts on each Shopify site and duplicate all the information?

With Uber you have one account which you can use to get a ride anywhere in the world, or even get food anywhere in the world. The same applies to Airbnb: one account, anywhere.

Why doesn't Shopify work this way?
Oh wow, did not even know you could enable by default on Safari mobile. I really like this!
What US society is struggling with is what to replace church with. It provided community and mutual support, but combined it with a myth that many could not accept any longer. The big question is what can provide the community and mutual support without the binding myth. There hasn't been a replacement thus far that has taken hold.

Also, the combination of online life and recently the pandemic has weakened what local community life still exists.
I feel like whiteboarding has only gotten popular in the last 10 years, maybe less. I've been at six companies in that span, interviewing at probably 12-14 total.

Out of the six, four have been tech startups including the one I am in now. The industries have been cybersecurity (x2), online retail, and online marketing.

The two non-startups have been in education and healthcare.

2016 was the last time I didn't have the luxury of looking while jobless, but I was still pretty picky. I already knew I didn't like white boarding, so I started to warn recruiters that I wasn't good at it. Two early interviews, I told recruiters this, and they both urged me to go to their interviews anyway. I went ahead thinking it would be good practice.

Not surprisingly, I wasn't offered because I just wasn't that interested, and it showed in the interviews. I remember getting a bit curt in one interview because the last person that I interviewed with (going on 4 hours), asked me the same coding question as the first person.

After that experience, I became more inflexible on my no-coding interview requirements. It probably was just dumb luck, but this wasn't a problem, I was told. Two more companies after that were at companies that did architecture interviews centered around data platforms, and I eventually took one offer.
Free speech has seen less value to those in control of the cultural zeitgeist. Unfortunately, the American populace seems to agree there.
>It is etymologically correct though: condition of being worthy, dignity, glory, distinction, honor, renown.

The etymology is not even close to being relevant. Conflating two different meanings of the word "worship" and implying their equivalence is dishonest and deeply unsound. That is true even if it is the definition of worship fits in both cases.
It’s not. It’s so technically detailed in some aspects yet others (missing police chases , the missing train, the minimal that doesn’t zoom out when you’re in a car) are worse than GTA San Andreas from the early 2000s.
> No it isn't. It's a tactic used my sales weasels to gain leads.

Thanks for the broad assertion, and your weasel words! :)

Your point that it's used by bad people is valid -- I agree with you. There's a lot of bad stuff about the tactic of not revealing price, and certainly a lot of bad actors out there who will use it to eke out the best price they can, or for numerous other bad reasons.

Unfortunately for your argument, you can't really assert the negative here: that no one could hide the price for a good reason, because you can't know 'em all. There are good reasons, as I outlined, and there are people who've chosen not to display their price for reasons among the ones I listed. I know some of them, multiple firms, and I know intimately that these firms do not e.g. change their prices depending on who they're talking to. Some places might! But these ones don't.

Often they're early businesses proving themselves or new products out. They want to focus on leads who've expressed a clear signal of intent, price isn't the strongest selling point of their product, and they want their great product to shine in the areas where it is most competitive.

Price is not always what matters most to a buyer, especially an institutional or commercial buyer, but people are strange about money. Upon seeing a $100 difference on a thousand dollar purchase, someone might choose the cheaper product because they think it's a "better deal" without having ever investigated both fully. If they'd looked a little deeper, maybe the higher cost thing had a far higher value? It can sometimes be hard to articulate that value without digging in a little, or learning about someone's problems. But haggling on price is a little bit like bike shedding -- it's simple: lower is better, so it's easy to focus on.

So as I said, it's a reasonable tactic for some firms. They aren't necessarily hucksters, they're just rational people doing what they can to compete. Maybe someday price will be an attractive part of the sales strategy, but... today it's not, so it takes a back seat.
There was that famous Amex case in the 80s where through some massive misunderstanding the restaurant (I think) got mixed up using the terminal and accidentally entered the long number for the amount. It being the early days of those terminals, the cardholder didn't notice and accepted it and Amex let it go through as it was one of their no limit cards.
The overnight interest alone was astronomical. Fortunately Amex saw the PR value in being decent and refunded everything.
Nginx as reverse proxy does this and it's burned me.
He was not wrong.

What is wrong is to allow Federalists into public office.
Thanks for the response. I appreciate it.

Here is my take away from this: that's overly complicated.

We all have a finite amount of time. Most of use allocate 8 hours of the day to work. With that in mind, and given we have a team of 5, we have 5 * 5 * 8 - 200 - hours of (technical) labour per week.

Based on experience we all know that what we actually have in terms of time applied to problems is closer to 5 hours. Let's say we agree that's the truth. So we now have 5 * 5 * 6 or 150 hours of skilled, technical labour per week.

Taking a unit of work, a problem, and assigning it to someone creates the context for determining how long it will take to do. Whether or not Janes can work faster than Bon has nothing to do with it, in my opinion.

Bob can solve the problem in two days, or 16 hours, based on his experience and skill. Jane can do it in 10 hours. So give the job to Jane if it's urgent, or to Bob if you can wait.

You know what exactly to expect based off of this simple process: you've lost Bob for 16 hours.

I feel it doesn't need to be any more complicated than this.
Does that matter?

Tremendously. Just as the Robinhood CEO and watch videos on the mechanics of why they did what they did. Then come back here and hang your head in shame.

Lucky thanks to trust and centralization it can be resolved instead of lost forever.

It's the centralized systems of disparate parties which causes this. You clearly don't know what you're talking about here.
I forgot about it and just found opportunity to read it in full. My tone in referenced reply was uncalled for. I would edit for civility if I could. I'll filter my posts on topic for pejorative language in the future. I appreciate the the effort you put into explanation. By abuse, do you mean focus on one flamewar topic? I engage in topics I'm well read on, or rather I get engaged on topics where I have dissenting opinion. Most of my comments on other topics typically don't get any replies so I find most of my followups / replies to centre around Chinese topics. I will incorporate your two guidelines going forward to avoid engaging in ways that bias towards flamewar.
There are good suggestions from others. I just want to say sorry if I came across quite harsh. I respect that you’re doing this at all and wish you the best of luck.
It is fairly simple imperative code: you just call functions on everything.

Where it gets more complex is data and fitting that into an imperative model with very few flow control constructs: updating, creating multiple elements at once, doing weird things like calling select on elements that don't exist yet, and for most chart types there is a topological ordering on the graph of actions required to create a chart (i.e. you have to create an axis before you create a line because you need the axis that maps your data points to x,y positions)...combined with the fact that d3 throws almost no errors or misleading errors with bad inputs, and it can definitely great pretty tricky. The saving grace is the dispatcher which you can use dispatch events, and this does make it possible to break up your code.

Also, it is nothing like React. Trying to get d3 working with React is like trying to stuff a sausage through the eye of a needle. It is a great package but it is becoming a bit outdated as the world moves towards things like React. Also, for most users it is superfluous. I still use chart.js, and only move things over when I have problems.
> this could technically be written as draw.circle(150, 77, 40)

No. It couldn't be. Because circle is an element of a tree so you'd have to pass in the parent node.
> the easiest path is to pick "boring" technology that still super valuable to the business, with a long shelf-life, but not sexy.

Would PHP and Ruby still fit this? Not just the "boring" part but also the long shelf life? These have been my main standbys but a lot of things in the web are moving away from them. Should I jump back to things I haven't used in a long time? I don't know how much Magento has changed over the years but I get some recruiter emails about it, even 8 years after I last used it on the job.
None, speculation.
Curious what the end result was though. It appears they collectively agreed to talk it out in September, then... nothing? Github shows a handful of commits, but nothing major. No chatter on the mailing list.

NetBSD hasn't renamed "wireguard" which they said they were considering as an option if Jason was going to keep pushing back on the existing code. The lack of major changes to the code makes me think they also didn't take him up on his offer to scrap the whole thing and start from scratch or port the OpenBSD implementation.

Anyone happen to have any further insight?
Of course not, if there'd been proof, we would have seen a whole different article.
Thanks, I agree 100%. Perhaps I'm getting unnecessarily cocky in my old age, but this really does feel like other cases I've seen in the past where people (including the original founder) want "a clean slate", because of course there are warts and lessons learned from the original implementation, but the cost of workarounds for those warts is actually lower than the cost of switching to an entirely new competing technology for most people. Going back to the original list:

- Typescript as a first class citizen: Agreed, it's not hard to get TS set up in Node, and it's a "one and done" cost.

- An actual `window` global with familiar browser APIs: I've never needed or wanted this, though I could see how the server-side rendering crowd could benefit, but I still have to believe there would by necessity be enough difference between the browser-based window that implementing SSR is still non-trivial.

- Sandboxing w/ permissions: I honestly think this is going to be useless. As you stated, if you're really running untrusted code better to rely on process permissions. This actually reminds me of many of the overly complicated security/permissions architecture in the Java SecurityManager stuff that I rarely if ever actually saw being used.

- URL-based imports (no need for NPM): NPM certainly has its warts, but I think a lot of Deno supporters woefully underestimate how most server-side JS developers love having a single primary global package repo.

- Bundling into self-contained binaries: Again, this is nice, but also gets a "Meh, I don't really care" from me.

- Things like top-level-await which Node.js still treats as experimental: Once you learn how to do an IIFE who really cares?

- Better-designed APIs than the Node standard lib (esp. when it comes to promises instead of callbacks): Again, a minor nice-to-have, especially with Util.promisify.
I think you can more easily convince me that D3 and React don't go together at all, because their models conflict, than that it makes sense to code directly to D3's guts and replace a lot of its logic with React's. But you all have more experience with this than I do (I've used both in anger independently, but not together).

There's a point in this article where they've replaced D3's axes code with a new React implementation. "Okay! So this is definitely more code. But that makes sense, since we're basically duplicating some of the d3 library code, in our own code base." I mean, yes. It makes sense. But it is, ceteris paribus, way worse than D3, where axes generation is kind of a fundamental basic idiom of the library, which we're here replacing with idiosyncratic new code.

I get that the code might be better in some other direction, but just as code, it's worse. The claim is that it's more readable, but: it's only more readable if you don't do a lot of D3. To me this is shades of people trying to talk about Lisp function names or APL or whatever.
> It's an interesting structure...

I think that's the question. I'm very much used to reading "A machine-readable medium, comprising..." I'm curious what bits are unique to COVID-19, and what bits are generally protecting the idea of using a carrier to send a specific protein. In this case, is it the "S" protein phrasing that protects the specific embodiment of COVID19's spike?
In the "old days", web pages were often just the bare content (no html, head, body containers, no DOCTYPE declaration). A few sites also featured just the body tag (and respective content) for setting the background attribute for the page background color.

E.g., this is the entire code of Netscape's first home page:

<TITLE>Welcome to Mosaic Communications Corporation!</TITLE>
<CENTER>
<A HREF="MCOM/index2.html"><IMG SRC="MCOM/images/mcomwelcome1.gif" BORDER=1></A>
<H3>
<A HREF="MCOM/index2.html">Click on the Image or here to advance</A>
</H3>
</CENTER>

http://home.mcom.com/
The name tachyonic antitelephone is a bit unfortunate because it need not involve tachyons. All it takes is the ability to send a message outside of your light cone. Along the path actually taken need not be the case, we are reasoning about the endpoints of the communication independent of the means.

In particular it does not matter whether you use a warp drive or not. The violation occurs relative to reference frames outside of the warp bubble where special relativity fully applies. Here, explicitly looks like a worked out example: http://exvacuo.free.fr/div/Sciences/Dossiers/Time/A%20E%20Ev...

You can create instances of FTL travel or communication that don't violate causality. But the ability to perform such FTL tricks implies the possibility of constructing a closed timelike curve so long as you're talking about a localized phenomenon like a warp drive or tachyon where special relativity holds outside of a negligible area.

If you're messing with the global geometry of spacetime then you can make very weird things happen and I would not be surprised if there were such a geometry that allows FTL communication in a limited way that doesnt allow CTCs. But that would not like our universe or a warp drive, a specifically localized situation.
Viewing pornography is equally as likely to be grave sin (I say equally likely because the act is a necessary but not sufficient condition for meeting the definition of mortal sin). I don't mean to downplay that pornography is a negative influence, but you misunderstand mortal sin [1]. Paragraphs 1854 -1864 are particularly relevant.

Mortal/grave sins must be confessed per catholic doctrine, but to say that the mere acts were final is to misunderstand the whole concept of the new covenant.

[1] https://www.vatican.va/archive/ccc_css/archive/catechism/p3s...
Don't give them any good ideas
> In Lua API, all Lua values are bound to a stack, and C functions have to exchange values via that stack - there's no free-standing "Lua value" type in the API.

That's not 100% correct. You can have values unbound from the stack, they're just typed, rather than having one "value" type. (lua_Number, lua_CFunction, etc). Though functions bound from do still use the stack for taking/returning values. (However your C functions can directly work on other value types).
If our population was better educated, I feel like togas, buggery and acropolises could be a real option.

Not more degrees, but well read- history, philosophy, religious literature, science shit, etc.

Also, the whole wokespeak has seriously destroyed public discourse- not just from the right but on the left.
For one, ZeroTier does not necessarily want to authenticate you via a public OAuth provider. I'd rather not rely on it where not strictly necessary.

Then, ZeroTier does have a free tier, with open-source clients for every platform I care about. Yes, they are limited to version 1.x, but maintained nevertheless.
I think shareholder supremacy is from Milton Friedman, who promoted the idea of the share price as the important thing to observe, leading to the use and misuse of strategies like stock buybacks:

https://en.wikipedia.org/wiki/Friedman_doctrine
This is how it works. Once you enter your email or phone number, in a store that supports it, it will remember the rest. I get a text now once my phone number goes in with a code, enter the code and I'm done. See also: Shop app.
An interesting aspect of China's green energy activities is the historic role that coal has played in the revolutionary imagery of the communist party. The coal lobby in the US is powerful, but not in nearly the same way
Thanks for the insights, it's going to be an interesting time as we get back to normal (I hope)
Recognized my poor squibbles better than my parents.
That money is "floating around DeFi" has no bearing on Visa opting to settle transactions in USDC. They're not getting into DeFi lol, unless you have some unreleased memo. Do you have data to back your claim that it's the "fastest growing financial sector"? By what measure? What metric? Your replies are hyperbolic at best, and read a bit like like zealotry at worst.
Do I need to have qualification for the job? If not, F1 team mechanic.
> How are you planing to send that power to, for instance, the United States? Disregarding the massive infrastructure requirements, there are serious power losses.

I just got into this discussion the other day here:

https://news.ycombinator.com/item?id=26599340

A commenter estimated the losses from North Africa to the United States to be about 33% with high-voltage DC.

Wikipedia says this:

Depending on voltage level and construction details, HVDC transmission losses are quoted at 3.5% per 1,000 km, about 50% less than AC (6.5%) lines at the same voltage.

https://en.wikipedia.org/wiki/High-voltage_direct_current

North Africa to North America is somewhere in the ballpark of 10,000 km. (1-0.035)^10 is almost exactly 70% (i.e. 30% loss). So, that actually sounds pretty reasonable.
There were major providers that at one point in time overrode TTLs to a minimum week if under 24h.
CS interviewing theater.

Linked list Q's are great if you're interviewing embedded sys engineers writing low-level kernel code in C and need to keep track of resources. In that case, I would see if they could also implement a 2D infinite sparse matrix.

Test for what the job requires, hopefully real-world problems using sequences of open-ended questions. Everything else academic or immaterial to the job might just be a mental shortcut or Lemminging everyone else.

Perhaps run through how to talk to and provide customer service to non-technical stakeholders if those exist.
>There hasn't been a replacement thus far that has taken hold.

The replacement is social media.

Is it a good replacement? Absolutely not.
ok, that's fuckin hilarious
The ones for sale are the small perimeter lidars that have very short range, not the 300 m unit.
Wow. Load times are incredible and no stupid node.js present
It's interesting that none of the finalists for this US standard appear to be from US authors?
Don’t think so.
Low bar is not always wrong.
> What would be the purpose of loading disintegrating box anyway?

Sometimes you're unloading or on the receiving end of disintegrating boxes, and you need to unload the container the freight came in. This is to receive in the damaged product to your warehouse before you can claim it.

Two examples I from bring on the receiving end:
- ocean freight were water gets in through holes / damaged parts of the container that cause all the packaging material to breakdown
- beverages being punctured or otherwise leaking causing all packaging material to be damaged

In an ideal state, you don't have damaged packaging because you can use clamps, slips, or other specially designed conveyance equipment.
The smallnetbuilder review of AC68u goes into detail on this. But I think newer wifi routers have fixed this that support USB ports.

http://www.smallnetbuilder.com/wireless/wireless-reviews/322...
My cat went nuts for that. "Entertainment for cats." is right. She's still looking for the bird.