skysight-inc/HackerNews huggingface dataset:
Advice like this is always funny to me. It's kind of like being upset about the low quality of vegetables at the super market and being asked why you don't just grow your own in your backyard.

I'm sure anyone who is technology savvy could switch to Nextcloud easily enough, but that isn't the point. Dropbox was probably chosen because the money is worth the convenience.
For what it's worth, they seem to be hiring lots of developers at their tech centre in Markham, north of Toronto.

I'm not sure where these developers fall under GM's corporate structure, though.
In the Web PKI, which is what you care about:

A certificate can have an effectively unlimited (CAs impose an arbitrary limit like 100, nobody is sure the maximum that could work) number of names listed (the subscriber will have to achieve proof of control for all these names to get the cert).

Each name can either be an exact fully qualified domain name, and will match only that single name, or it can be a "wildcard" like *.example.com which matches any DNS name with exactly one label (a part with no dots in, essentially) where the asterisk is and the rest an exact match.

Thus, a wildcard in com, even if it could exist (it is forbidden to issue such a thing) would not match service.example.com only the exact name example.com itself.
Does quantum mean its thread safe?
"available next year"
That makes sense. gotos make code generation so much easier, and computed gotos are even more powerful. Lua 5.2 added goto precisely to make it easier to machine generate Lua code. WebAssembly lacks gotos and it's a serious impediment--compiling to WebAssembly requires a special "reloop" algorithm which, while conceptually simple for most code, doesn't work well for the type of critical code for which using goto and especially computed gotos are useful for. Reloop doesn't always work and so sometimes the only way to compile to WebAssembly is to add indirection, such as compiling to an intermediate state machine.

I think WebAssembly originally required reloop because it was originally designed as a purely stack-based VM with properties that made it trivial to verify the bytecode (similar to BPF). Then things got much more complicated for performance reasons and I feel like they probably could have added goto support at that point with little marginal complexity. It's clearly possible--Ethereum did it, BPF permits forward jumps, and eBPF permits both forwards and backwards jumps.
> Add a step immediately after parsing the regex, check if it is regular and can be handled by an engine like RE2, otherwise handle it using the normal regex engine.

This would be a bad idea. For one thing, it would be slower on non-pathological cases, since backtracking is faster in practice. But more importantly, devs who test on Chrome might unwittingly create regexes that would run exponentially slower in other browsers.
This data is weirdly bucketed and the fit curve looks sketchy. I don't think it's a robust finding and I don't trust it.

Doesn't seem to have stopped a lot of people confirming their anecdotes though.
Blockchain Real Estate: $20M to “Tokenize” Student Residence
I understand. I just do not accept the incidental complexity and performance tradeoffs these SPAs mean. I have built several of them over the last couple of years but still like to avoid them as much as possible.
I managed restaurants for a few years. One consistent mistake that I saw, was that restaurant owners would rent more space than they needed. I think the owners over-estimated how popular things were going to be.

Because of this, one of the easiest ways to improve your odds of success, when you own a restaurant, is to lease LESS space than you need. Basically there's a lot of good reasons to make your customers wait in line:

1) You're not paying to rent the sidewalk in front of your restaurant

2) Having a few customers waiting out front is a great advertisement for your place.

Obviously, this isn't great for customers, but if you're a restaurateur it's awesome.

Out in Vegas, restaurants and clubs routinely pay people to wait out front to make their place seem "in-demand."
First match, then capture. All captures are wasteful unless there’s a match.
Harry Leslie Smith Has Finished His Last Stand
Passive daytime radiative cooling
As the creator and maintainer of a project, it's really hard to let go of said project.

It's really hard to completely abandon a project you know people are relying on. You do feel responsible for it in the end.

Also, nearly every time someone opens a ticket, it points a deficiency in your project, and it's somewhat hard to accept that your project is not "perfect" (spoiler alert, it never is). Consequently you, as a maintainer, always want to fix issues or implement obviously missing features.

Also publicly admitting that your project is abandoned (by an header in the README for example) is quite hard, it feels like a failure and at least, you are publicly admitting something with a negative connotation.

"Maintained" forks that take over the initial project are extremely rare.
In most cases, a fork will be tiny modifications done to fit one user's specific need.
Nobody really wants to factorize these modifications into a common solution and maintain it.
Well maintained forks do happen, but only for highly projects.

I'm speaking out of experience, I maintain a bunch of projects, not highly popular ones (a few dozen stars on github), but definitely used by other people. And in these projects I've a few that I definitely have nor the motivation nor the means to really maintain well.
Typically I created a puppet samba module that is quite successful, but I've not used Puppet in 3 years, so I'm not a consumer of my own software anymore and I've not followed the evolution of Puppet in years, yet, I've not set my mind on publicly stating that this project is not maintained anymore.

Lastly if I do get PR for these projects, these are generally not really complete quite complete, documentation and unit tests are always missing, and the code quality is rarely on par, specially if the PR is quite complex. For every PR I accept I generally have a few commits to complete it/fix it.
This.

When I see something like this:

https://techcrunch.com/2018/09/24/walmart-is-betting-on-the-...

I just don't get it.

I understand the motivation behind them wanting this sort of broad supply-chain tracking, but I don't see what "blockchain" actually solves for them that can't be more readily/efficiently solved in other ways.

A trusted third party, with an immutable transaction ledger, and a simple to develop to set of APIs seems far superior from a product perspective in a case like this rather than those solutions that will simply build this same thing on "blockchain" software. The only gap is an API which is domain specific (like for food supply chain).

(And even this won't solve many of the trust issues in food supply chain, but it looks like it will offer the same useful traits of a blockchain only more simply).

[edit for clarity]
Botpress Server (v11) – A Chatbot Maker and Bot Development Framework
Thank you! Finally some reason.
Is off the shelf open source OCR not reliable for an image of reasonable fidelity, like a smartphone camera picture of a B&W text document?

I ask because it feels like I should have an app that lets me scan with my phone, process the text with OCR, then let me plain text search every scanned document I have.

The first part only natively made it into iOS Notes a year or two ago, but that whole experience above should be out of the box, IMHO…
don't forget about property taxes and HOAs. sometimes the property taxes can be higher than the value of the house. just watch out.
I'm wondering if this shares any technology with the CloudWatch metrics backend. They've been making improvements there all year, and most of them generally align with what's announced here.

CloudWatch metrics are also very expensive for what you get, so that's another similarity to Timestream ;)
What about the people on YouTube who make decent children's shows/cartoons?
Decentralized organizations are the future: why I’m joining Aragon
issues such as what?
Multi-company operation is the holy grail of private blockchain projects, but it's also too complex for people to manage.
Yes, the article states that the Mylan product can be purchased for under $150 with a discount.

In fact, several large retailers sell EpiPen for $150 when including a coupon, according to GoodRx.

As for the FDA narrative not being true, how do you know that? The article doesn't actually state the true cost of the Teva product anywhere, which was my original point.
If they’d throw in a working visa I’d be intrigued
Compatible with GPLv3, not GPLv2, to best of my knowledge
I’ve always found that if you stare at something long enough you can eventually understand it, and break it down into its core components. If your business depends on it, don’t be so quick to just rewrite it and abandon because it likely will have a ton of hardened edge cases that are baked into it that the business relies upon.

You must study the code and document what you can. Reverse engineering it is sometimes the only option in your quest to understand it. Then you’ll need to make decisions about how to move forward given the constraints of the business whether it be time, resources, other priorities. There is no one size fits all answer but don’t be shy about vocalizing the risks and making sure the business knows the pain points. Sometimes you have to sell the problem you now have and get buy-in to really do something to fix the mess.

One thing I’ve realized is that when people don’t take the time to document and write clean code sometimes it boils down to their idea of job security.

Other times it turns out the problem is there is no single owner of this code base and it’s been hacked to death.

Lastly when something is ugly, enough and messy enough...then you can just call it proprietary technology...I kid I kid.
It's still too early for most people to understand how amazing the concept around MakerDAO and DAI actually is. They will, but it will take a bit of time.
What exactly do you think the differences are between a helicopter and drone airframe? They're both unibody constructs built for lightness that are designed to accommodate cargo/passengars via some active lift system; calling it a different name doesn't make it a disruptive technology
Google does what it does - bad things included - thanks to the decisions of a small group of people, who is now also controlling Alphabet and its subsidiaries like Verily. It's perfectly rational to assume they have not changed the methods, management style and ethical boundaries that led to the disliked behaviors in Google.
I think of self-awareness as similar to the problems of achieving consistency in a distributed system: it takes a lot of work to get right, and even then you probably missed things.

Upton Sinclair wrote, "It is difficult to get a man to understand something when his salary depends upon his not understanding it." In my experience, when people have a strong financial interest in not being self aware, they will generally not be self aware. I can never decide whether that's legitimate or not.
How ‘Mr. Hashtag’ Helped Saudi Arabia Spy on Dissidents
i don't know why this is being downvoted. the core idea is a good one. Start moving people away from expensive areas and have them populate areas like the rust belt where housing is much cheaper. Detroit is pretty cost effective as others have mentioned.
>> Maybe something like this is why whites commit suicide so much more than blacks in America

> Whites officially commit suicide more than blacks because blacks who are even slightly inclined to self-destruction find it all to easy to get into situations that produce death by means that won't officially be viewed as suicide.

Do you have any data to back that up or any type of non anecdotal evidence? Not attacking you. I actually want to know but I don't believe the, "Your data is incorrect because the way you collect data is flawed. However what I think is correct even without any data." argument is particularly strong.
I mean what you say in your edit. Even off-patent drugs require basic proof that they are what they claim to be, are similar to the patent drug in important ways, have a safe formulation, require a company to make a production line for it, and even require some marketing in many cases to make sure people know there's a new manufacturer of that drug.

I've never worked in generics, so I'm certainly not an expert, but I am saying both that we need some of the safety and quality controls by the FDA (or some system to replace them without relying on companies' good will) and that there are big hurdles even disregarding the FDA or other regulatory bodies.
Yes, but given the trend of quantum computers, it's confusing using that word freely.

Case in point, the whole reason I clicked through on this was becausei thought it might be some earlier quantum database.
The definition of "extraneous" is "irrelevant or unrelated to the subject being dealt with". The user was talking about Amazon. How can the fact that they work at Amazon be irrelevant or unrelated?

> Bringing those back into a different context to get the upper hand in an argument is a breach of civility.

Is it, though? I'm just thinking of applying that same argument to other situations in life and I don't know if it works. Is it a "breach of civility" for employers to look at your past work experience before hiring you? Is it a "breach of civility" for voters to consider the past political record of candidates when evaluating them for office?

I would argue that bringing in historical information from a user's past discussions is not "bringing those back into a different context", it is enhancing the current context. Mentioning that a user works at a company, while in a discussion about that company, is providing additional useful context to that discussion.

> I wouldn't call that comment astroturfing, either.

We can agree to disagree then, I suppose. The definition of astroturfing is "the practice of masking the sponsors of a message or organization to make it appear as though it originates from and is supported by grassroots participants." Again, that fits, to a tee, what the user was doing. He attempted to mask the sponsor of the message by lying about not working for Amazon.

I'll agree with you that I shouldn't have called him out in a comment. I put it in a comment because I wanted to give him a chance to edit his comment rather than his whole comment being hidden/removed (since his comment did provide good info), but perhaps should have just flagged it or emailed you instead. This interaction doesn't give me much faith that anything would be done about it, though.
Just because there is a job posting doesn't mean there is position open.
Adam Jones in Burnt would disagree with you.

"....the problem with this place is it's too consistent. And consistency is death. A chef should strive to be consistent in experience, but not consistent in taste. It's like sex. It's like, you're always headed to the same place, but you got to find new and dangerous way of getting there."
There's real vlc app in both Windows and WP app store. In fact there were two official VlC apps for Windows Phone. One was written with c/c++ and the other UWP version
FROM THE WEBSITE:

What's new in Botpress Server
There are 4 major differences between Botpress X (10.x) and Botpress Server (11.x).

- v11 is not an NPM library anymore – it is a standalone application. We distribute binaries of v11 for OSX, Windows, Linux and Docker on a daily basis.

- v11 now supports multiple bots natively – thus the naming of Botpress Server.

- v11 is a complete backend rewrite to TypeScript. We have made significant architectural changes that are not backward-compatible.

- We introduced our first version of Botpress Native NLU
In addition to canceling sound, the headphones actually block a lot of it to begin with, so they only have to cancel what's left. On the gun range, it's pretty popular to use quite the opposite of noise canceling headphones. They actually amplify sounds at normal human speech levels, then cut off anything above a certain amount. They make no attempt to cancel the gunshot sounds, they just don't reply them inside the headphones. And the blockage from just the physical headphones is enough to turn a deafening gunshot into something fairly comfortable to listen to for quite a long time.
Starting a construction / rehab company might work.
> Since the Nazis reset the codes nearly every day, the teams started from scratch each morning. Decoding them was a tall order, because the permutations were complex: Each rotor had 26 possible positions, and no letter was encoded to itself.

The permutations were very complex, but the fact that no letter was encoded to itself was actually beneficial to those decrypting the messages. From Wikipedia [0]:

"A major weakness of the system, however, was that no letter could be enciphered to itself. This meant that some possible solutions could quickly be eliminated because of the same letter appearing in the same place in both the ciphertext and the putative piece of plaintext."

[0]: https://en.wikipedia.org/wiki/Cryptanalysis_of_the_Enigma#Th...
>As a white male you haven't experienced any of that

This is almost unbelievably blind.
I agree, I was just trying to pick quick examples.

Last year I was in line trying to get into a college dance club, and a group of girls in front of me started screaming, one saying "I lost my phone! Someone stole my phone!" They turned and made face at me and started accusing me of theft. My friends were already in and I was alone in line, clearly minding my own business to anyone paying attention. But once they started screaming I had to defend myself by basically yelling at them that they were being stupid and to leave me alone. They started makinga big scene and people all around were getting interested. Just a bit later and the girl just pathetically says "oh I found it" and walks away with her phone, clearly unconcerned with the potential fallout against me.
HN Who's Hiring thread ~4 years ago.
What's New in DevTools (Chrome 72)
"Elbow grease" isn't going to fix major structural or infrastructural issues. I'm sure you were being funny, but most of those structures are tear downs.
It is perfectly possible to be conflicted about your product, in fact caring too much can be problematic for finding real product market fit. He probably does hate everything it stands for but loves building features that solve pain for his users.
This is how you build "new cities" [1]; pair startups with working visas and tie it together with funding and resource commitments (cough cough PlanGrid et el) to bring dilapidated housing back into inventory. Inexpensive corporate housing with you bootstrapping the culture and the community core.

[1] https://cities.ycr.org/
Web apps spend a lot of their time waiting for the database, for memcache, from their queue servers and so on.
I’m a consultant and make a living saving bad projects. That’s literally why I get phone calls for work. Keep in mind that I work in high level modern languages, I’m sure there’s some crazy proprietary cpu running a robot in a Detroit factory.

In any case there’s never been something that I’ve run into that I’ve not figured out. It takes time, and the hard part usually is not figuring out what it does but the weird edge case of the moon aligning with Venus and then the output suddenly changes. This is why understanding the requirements is more important than the code. I don’t care if the code is bad if I can more or less write a test case against it and make sure it does that.

That said complete rewrites never happen. It usually is only rewriting portions when that is cheaper than fixing. It is the if it isn’t broke don’t fix it adage.

The only time ever I’ve been stuck was when I saw a proprietary software implantation on top of a custom software package ontop of Solr (technically ontop of the JVM) create a large object heap issue ontop of a proprietary OS (Windows). It wasn’t code related I diagnosed that it was a GC issue, but it wasn’t in any code I had source to. A Windows update ended up fixing it. And this is why working with enterprise software is hard.
Our team inherited a tangled spaghetti mess of a client facing API. There were some additional requirements that needed to be added and we quickly discovered some serious security issues.

We considered a full rewrite, but this was too time consuming and did nothing to solve the immediate issues. It was also risky, we had a "working" production app.

We ended up writing an extremely thorough integration test suite. Making changes is still painful but we know for sure we aren't breaking anything. If we have the time/drive to rewrite the test suite could be re-utilized.
Not so much on a team, but when working on a difficult and unfamiliar codebase I usually start by taking a chunk and reformatting it to suit my style as though I wrote it. Spacing, indentation, bracketing, ect.

Once I've got it to a point where I can read it with minimal cognitive load (I like condensed code with little to no white space and no orphan brackets) I'll make sure it still works and pick a spot or feature in the finished application and try to find its code. Work backwards until I've figured out what makes it tick.

In the process of doing that I usually see how a lot of other things tick and get a sense of how and where the rube goldberg machine starts.

The hardest part is understanding the rationale of the developer. Many don't impart such details in the comments. For that I'll try rewriting sections with less code than the original and see what the adverse effects are.
The person using it (performing the injection) doesn't need any more training than an epipen, they are basically the same in that regard. You take off the cap, push it against the skin, and press a button. The slightly tricky part is loading the injector which would presumably be done by the patient well ahead of it actually being used.
That is essentially what I was hired out of school to do. I walked into a massive heap of ASP.NET (with VB) and MSSQL stored procedures that didn't really work at all, and had been through the wringer of a few cut-rate outsourcing groups. I struggled along with it for a few months figuring out how it was supposed to work and trying to duck-tape it together, doing a lot of support with customers that were trying to use it, and talking to them about what they were trying to do.

Then eventually I decided I wanted to learn some newer tech, so I started playing with Linq-to-SQL and ASP.NET MVC and Razor and Bootstrap, and over the course of three or four weekends and evenings I did a ground-up rewrite of the whole thing for fun. After a a bit more time flailing away with the old mess, I showed my side-version of it off to my boss, and it wasn't that hard a sell, being much prettier and less buggy.

It helped that there was nobody around who was invested in the old code base.

Generally, I've found it is a lot easier to effect this kind of change if you just do it stealthily and present it as a fait-accompli, because otherwise people get so bogged down in debate and fear that any impetus to actually take a risk and do something evaporates.
Cool, but I don't think I could get away with marketing a raspberry pi as a "quantum computer" because its bits change suddenly, discretely, and without intermediate steps.

Like it or not, "quantum" has accumulated a) more connotations that make it less likely to be interpreted as "sudden or discrete" by most people, and b) an association with other pseudosciency buzzwords that don't have a very good reputation in product names.
I like the `matchAll` feature. I now use the awesome/awful (depending who you ask) hack using `.replace`:

var matches = [];
"12345678".replace(/\d/g, (m) => matches.push(m));
console.log(matches);
This is kinda Amazon offering their own version of Eucalyptus, just 10 years later: https://en.wikipedia.org/wiki/Eucalyptus_(software)