skysight-inc/HackerNews huggingface dataset:
> Manufacturers are trying very hard to have built-in obsolescence

This would be a golden opportunity for a manufacturer to come out with a promised 5+ year support cycle. I think one of the reason they don't is because each manufacturer has 78 slightly different models every year to support, but in a maturing market they should have a better idea on what the market wants and cut that down. Why does know one learn the limited SKUs lesson from apple?

In that respect the Librem phone is arriving at almost the perfect time, it's close to PC levels of supportability.
Which externalities exactly?

With battery replacements and iOS upgrades improving performance, it seems like nobody has done more than Apple here, and indeed their stock price is even suffering for it.

What more are you looking for, honestly?
Thanks for sharing that.

We've just started a new Node project where typing was one of the main drivers and went through a similar thought process.
We use Flow on our client code but the positive chatter about TypeScript had made us wonder if we should re-think that.
We have similar thoughts on a lot of the trade-offs. Flow feels better at inference but the TypeScript ecosystem is amazing.

We ended up sticking with Flow for consistency (and we don't want to migrate the client right now).
It's good to know that a migration isn't impossible if we ever change our minds.
You appear to be making an ideological argument — I have no interest in engaging with that.

It seems deeply hung up on one particular and erroneous conception of race, while ignoring that there is an extant broad scale trend into clusters that roughly correspond to the groupings people had naively assumed. Historical conceptions of race were completely incorrect about the mechanics — but that’s different from there being no underlying phenomenon.

So the conclusion seems to be that racial essentialism is dumb (and I’ve said as much in every post), but that there are real biological trends and groupings that correlate to sets of features.

Absolutely none of your replies have addressed the question of if traits like intelligence are correlated to clusters that roughly correspond to the traditional conception.

Instead you’ve picked semantic nits with strawmen.
I can very easily add optional support for either 'fzf' or another fuzzy matcher. I'll take a look at implementing this in pure bash but I doubt it'd match the speed of a dedicated tool in this instance.

The current search is just bash creating an array using a glob 'list=(/path/to/current_dir/"$search_query")'. bash gets a lot slower when you start adding more levels to the search (2 or more deep).

I'll get to implementing fuzzy searching algorithms first and we'll see what steps I take from there. Who knows? It might work fast enough in pure bash for file searching.
So... like Lotus Notes, reinvented/respun?
I took a course on History of Science and I was pretty shocked to learn that Watson, Crick and Wilkins were deeply impacted by this book. That type of cross pollination between disciplines and generations of scientists is fascinating.
I found this PDF: https://www.ibm.com/ibm/history/documents/pdf/as400.pdf

> 1994
>A new generation of AS/400 computers called the AS/400 >Advanced Series is introduced in
>May, including the AS/400 Advanced System, AS/400 Advanced >Server and the AS/400
>Advanced Portable.
Scalia had a pretty narrow interpretation of the 4th, and believed that ‘conversations’ in general were not ‘persons, houses, papers [or] effects’, meaning wiretaps were not within the scope of the amendment.
Finally, a Problem That Only Quantum Computers Will Ever Be Able to Solve (2018)
This is the best part about data science, that should really just jump right out at you, and if it doesn't then please, please, please never try to apply data science to anything by yourself, because you will be sealing people into tombs of misery.

The point here, is that if you look at 1,300 shitty songs, and try to learn about what music is, with those as your example, you are setting yourself up to just make more terrible music.

Maybe a more readily tangible example is: if you were to try and learn about how to create fake dating profile images, but only learned with profile pics of ugly people, then all of your fake dating profiles will probably be unattractive, and they'll never fetch a second look, much less dates.

I mean, this guy cites:

Celine Dion
Taylor Swift
Pharrell Williams
Adele
Bruno Mars
3 Doors Down
Green Day
Lady Gaga
Gorillaz
Linkin Park
Avril Lavigne
Daft Punk

This tripe (and I mean tripe) has been forced down my throat for decades, and it still is incredibly terrible.

I don't ever want to learn anything about music from this music. It's awful. It all needs to burn. And if you locked me in a room with AI that learned how to create music with these examples as it's template, I'd probably climb the walls and eventually commit suicide. I mean, I'm half way there as it is, and yes, I do blame this kind of music, at least in part.
Not in this case. It directly relates to launching side projects without consideration for perfection which provides quick feedback.
The economic reality of building software is that it is enormously expensive. Yes, you could develop your own operating system, compiler, UI frameworks, databases, etc. Or you could use something that already exists and works and focus on creating something new instead. You'll never get around to building something new if you first have to reinvent countless wheels.

That's why there are only a handful of widely used operating systems, many of which are Linux based at this point and all of which depend on many small OSS components. It just takes too much effort to get to the same level of functionality. The two notable exceptions are Apple and Microsoft that both choose to maintain their decades long investments in their respective software stacks. Even Microsoft has recently joined the club and is now doing open source openly. Sound economics and it has done wonders for their valuation.

Another reality with software is that its value decreases over time. It inevitably becomes a commodity. Design, algorithms, and successful features find their way to competing products and inevitably one of them gets distributed under a very permissive license. As that happens, the way to differentiate and stay valuable (and relevant) is to improve what you do, how you do it, and how well you do it.

This is the economic problem MongoDB is facing: their added value is tanking and they felt they needed to make their already quite restrictive license even less permissive to be able to get more revenue from their users. This makes the product harder to use commercially unless you pay (which is intentional). However, this causes people to look for alternative solutions and causes many of them to find their way to competing products.

The predictable result: several competing products now offer more or less drop in replacement functionality with most or all of the technical features that made MongoDB so cool just a few years ago. Amazon just capitalized on that by launching their own (closed source) product.

The long term economic success of OSS is tied to its development community. This requires ongoing investments to happen. An OSS community is usually not a single company that owns the software but the collective of users and developers of the software that together 'own' the software and derive value from it. There are certain types of software projects out there that are so essential to so many companies that they thrive for decades and are pushed forward by companies and people pooling resources through donations, active contributions, etc.

This requires a pragmatic attitude to licensing. We just saw frenemies Google and MS join forces around chrome. That is not charity: they both have a big enough economic stake in that project to put their differences aside (which are considerable). The licenses are key to facilitating such communities between mutually distrusting entities like that. It fundamentally has to facilitate the software can be used freely by anyone; that is the basis for collaboration.
> It's well know that if you start using C# , your entire stack will generally be MS based...(SQL Server, Azure etc... )

That’s only because of
Microsoft fanboys nowadays, .NET core is a pleasure to use on Linux and AWS with a variety of databases etc
Thanks, that's the idea. The project is still young so don't hesitate to bug me with issues etc. I'm sure you'll come across some. :)
> Seems to work for roads, fire, police, water and sewer, muni broadband, most shared services.

You’ve never been to Chicago, eh?
Concat doesn't mutate the original array, so there is no reason the output has to have the same value as the original array. Typescript has chosen to implement it this way, but it's not a limitation of the underlying JS method. Saying it's wrong because it's how Typescript has typed the function is circular reasoning.

Consider the same functionality exposed as a function, it would seem be fine to type this as:

function concat(a: Array<A>, b: Array<B>): Array<A | B> { }
>then someone is not assessing the risk of building and living there appropriately.

This is the answer no one wants to hear.

For example almost 10 years ago Paradise almost burned. There was a grand jury review afterwards(that you can find online if you're willing to search some) that pointed out that the place was a tinderbox deathtrap and major changes needed to be implemented for safety.

The problem is populations in these places, along with most humans in general, like trees and shade and the idyllic beauty of nature. People would rather have a pine tree and bushes around their house, rather than a 100 foot cleared defensive parameter.
To add to that: a QKD with one-time pad[1] is proven secure. However, because many QKD implementations have low secret key rates (the highest in research is 10Mbps[2]; most commercial implementations do only a few Kbps) you won’t be doing high-bandwidth communication using that method.

[1] https://en.m.wikipedia.org/wiki/One-time_pad
[2] https://www.toshiba.co.jp/about/press/2017_09/pr1501.htm
No lol. Javascript is not a good language to compile to. People compile to JavaScript only because it's the only language to run in browsers.

Most compilers, after type checking and semantic analyses, basically generate a control flow graph with basic blocks. Javascript doesn't have goto so it doesn't allow you to express those low-level things natively, which is why emscripten has to include a relooper component to turn them back into loops and conditionals.

If you want a good language to compile to, look at LLVM. It's a language designed to be compiled to, and it's mind-blowingly easy to compile to than either C or JavaScript.
> Take it up with the Americans for fucks sake.

Look I am no big fan of the Chinese political engine, but maybe Canada overstepped. The arrest of the CFO can be seen as highly political motivated, and now China is showing Canada that it too can do the same thing and arrest citizens of other countries (maybe even on flimsy grounds) or in this case use it's legal system to pressure and manipulate international relationships.

Canada got stuck in the middle (as many countries do when they do the bidding of the US) and have now got a slap on the wrist.
PG&E had more than enough money to bury its power lines, and used that money to fund dividends and executive bonuses instead.
It's remarkable how much this still rings true today.

The idea that we should try and understand life as a battle against the second law of thermodynamics has had a significant influence on many of today's great thinkers - such as Friston [1] and Dennett [2], as well as countless others.

[1] https://royalsocietypublishing.org/doi/full/10.1098/rsif.201...

[2] https://www.youtube.com/watch?v=iJ1YxR8qNpY
Flash cells leak and degrade. Some firmwares also have bugs - not refreshing cells frequent enough even if the drive is powered. The leaks are even worse on high-write-endurance enterprise drives. Make sure you read the specs and don't expect to be able to read without errors a SSD that was offline for 1-2 years.
What about a second factor for TFA?
Definitely. I'm turning the last corners on the mvp, and very eager to put it in front of people.

I very much want to talk about it, but it feels a little meaningless to do so until I've shipped it :)
Yeah, because someone would build a second distribution line next to an existing one.

Can you imagine ever house with 10 wire pairs coming in from the street, one from each utility?

Competition on distribution or transmission is simply not going to happen. But it can - and should - happen on generation, as it already does in a lot of markets around the world.
Born, raised, own several rental properties in the western suburbs. Recently renovated tollways are 100% well done (especially the LED lighting), and the MDW expansion is going to be glorious when it's completed. Is there a cost? Sure. Society costs money. Is there corruption in the process? Sure. We're working on it.
Ah... that makes sense. I have experimented a bit since my original comment and so far have not been able to come up with a syntactically elegant way of implementing LEFT JOIN in an imaginary MySQL that had inner JOIN as the only JOIN. This actually makes me wonder... if SQL only had inner JOIN, what would be the syntactically most elegant way of implementing the other JOINs? The various replies in this comment tree make me suppose that the answer would depend on the precise flavor of SQL being used.
I had built a layer like this one for my startup Bagcheck called Havrobase[1] (it was on top of HBase/Solr, here is the motivating blog post[2]) that ultimately I put on top of MySQL/Solr and other stores. Later, when we started Wavefront, I ported that layer to FDB and that still powers their metadata. Really a good fit and very much like this record layer. I highly recommend this approach for 24/7 services as you never need to have maintainence windows for schema upgrades and the like.

[1] https://github.com/spullara/havrobase
[2] https://javarants.com/havrobase-a-searchable-evolvable-entit...

Initially at Wavefront we were using HBase for telemetry, Zookeeper for the service mesh and MySQL Cluster for entity metadata. All that was moved on top of FDB with 3 different layers that we developed.

I'm excited that this kind of database is now going to be available more broadly and with the confidence that CloudKit is using the same technology since to date implementing something like this was basically a DIY project.
Useful article. I really wish startups put a lot more thought into making their team/culture remote ready from day one.

Reading this post is a great step in that direction...
The argument is that you have a potential type error in `a.concat(b)` that you hadn't considered before in that code: If `a` is defined everywhere as Array<Leaf> and you push() something to it that is not a Leaf you potentially broke one of your own invariants somewhere else that uses `a`. In JS concat happens in place and is a mass push, so the same general concept holds.
Several cities / regions in CA have their own electric utilities

Few big issues with SMUD, MID or TID
Good magic, bear in mind: It's usually really obvious how it works, unlike C++.
How is that utterly useless? It's pretty clear the intention is to prevent a) people being prevented from leaving enmasse and b) revoking their passport.

This is basic stuff and doesn't work in a vacuum you can safely assume we live on the same planet that happens to have mostly open borders.

Regarding the customary international law thing it was not refuted at all. It says that it does not constitute international law for the USA, and does not constitute domestic law for some [citation needed] other countries - likely because of the vague at times wording.

The fact some nations dispute it doesn't make it any less customary international law, hell it's kind of the definition otherwise it would just be international law.

https://en.m.wikipedia.org/wiki/Customary_international_law

Customary is just that, it doesn't have to be upheld but it can be used as a moral guide to defining and shaping other laws.
Not terrible, but there are a few problems with this list...

1) it advocates for use of "hosted" password managers which are a Bad Idea for obvious reasons

2) it recommends centralized 2FA using 1password/lastpass... in addition to 1 above, storing your 2FA info together with your password effectively makes 2FA completely useless

3) it wants you to use 1.1.1.1 for DNS resolution, which is arguably a terrible idea given Cloudflare's recent shenanigans.. while better than using your ISP's resolvers, running your own recursive DNS resolver is really the best "medium effort" option, and it isn't difficult (for the kind of power users who'd be reading this sort of guide)

That being said, I liked the site layout and collapsing-tickboxes -- they make the list very usable. I'd love to see this format applied to other lists in various places, where ticking off an item automatically hides details about it.
The end of marketing phones as fashion devices. Phones should be seen as tools and they should be expected to last about 8-10 years. There is no reason they can't other than apple and the rest make a lot of money on people throwing out working phones to stay on trend.
ty for the response, makes a lot more sense now.
watch ls
Gozala/wisp: A Little Clojure-Like Lisp in JavaScript
The linked page on Alerting Principle there is good:

https://response.pagerduty.com/oncall/alerting_principles/

"We manage how we get alerted based on a simple principle, an alert is something which requires a human to perform an action. Anything else is a notification, which is something that we cannot control, and for which we cannot make any action to affect it. Notifications are useful, but they shouldn't be waking people up under any circumstance."

They also distinguish between "needs fixing right now", and "needs to be fixed asap, but can wait until office hours"...
I use Flow at work, and have plenty of experience with both statically-typed and dynamically-typed languages. I think it's a simple tradeoff- more certainty for more toil.

It can be a real chore convincing Flow that working code works, and this can force you to use less-readable idioms to make the typechecker happy. It also lards up your code with extra dollar signs, angle brackets, and other crud, making it less readable.

These can be acceptable costs depending on your project, particularly the size of it (in lines of code, components, number of engineers, however you care to count).
author here

thanks for posting the article on HN -
i am a daily (more or less) lurker and a huge fan :)

let me know if any parts in the article aren't clear or major points are missing - happy to extend or answer here
That's actually not coming from the hat, you're receiving signals of the site's impending collapse through the foil. You way want to consider adding a few more layers.
IObit Driver Booster Pro 6.2.0.200 Full Crack with Serial
YouTube just changed how you navigate videos in its mobile app
So their practicing of unsafe sexual practices would have justified the ostracization?
You're talking about T&D redundancy when I'm talking about an open market of competition. You don't have to have T&D redundancy to have open market of competition. If you live in an area with an abundance of sun and wind, you can buy your local T&D and provide competitive pricing to your market. You cannot do this when there's a state-granted monopoly.
On the contrary. It was private industry that electrified the US. Samuel Insull realized that the way to achieve inexpensive electricity for everyone was to have much larger power plants than people were envisioning at the time. The logical conclusion of this was to create electrical monopolies that were regulated. He electrified Chicago and a large swathe of the country at a breathtaking pace.

So, no, the government did not create the electrical system and then privatize it. It was private from the get-go, and when utilities became monopolies, they were regulated.
Natural catastrophe review 2018
The author of OP article really needs to read that Toshiba press release. Good layman explanation.

Also, I figured that the bottleneck came from the amount of entangled photons that could be generated. Interesting to know that it's a hardware/software issue on the detector and post-processing side.
Probably 2FA at Pinterest [1].

Actually, on this topic, I'm planning a talk on how to build 2FA (specifically how to add 2FA to an existing site/app). If you need to implement 2FA or are interested in this topic, what would you like to learn from a talk on 2FA?

[1] https://medium.com/@Pinterest_Engineering/two-factor-authent...
Americans more likely to die from opioid overdose than in a car accident
Yes it is! Sorry for not linking it and thank you for doing so!
Might be more interesting to analyze the progressions in the real books. Or by time period - pop music in the 70's was more harmonically advanced.
Which means there is a third party eavesdropping on chat.
It's more correct to say that you shouldn't ever get divorced in a community property state. If Amazon were based in Texas, it'd be a very different situation. When it comes to divorce, it doesn't matter where you made the union, it's where you're dissolving it.
"Forensic science" has a long history of being flagrant psuedo-science, very often being a morally bankrupt abuse of statistics.
This is a pain point that the community wishes to address: https://github.com/tc39/proposal-javascript-standard-library
I learned programming on some old AS/400 in school. The server was standing at the local state office and we had an ISDN connection there from school. I remember the manual stack, it was a couple of meters in the shelf.

We used 286 computers with windows and a terminal emulator that converted the control buttons to enter.

The server was shared with the states programmers as their test server so we had to wait our turn for compiling and running code. Could be a good 20 minutes to get the output of the program on the printer sometimes :-)

Tried getting a job as an RPG programmer in some companies in the area but all that was about to buy one ended up going with PC's instead. And the ones that had an AS/400 decommissioned it so didn't need programmers. But I did some work for the state, like fixing the y2k bug with birth year in the database :-)
If you so choose to D can have a relatively clean library implementation. The type inference isn't bidirectional (Or at least it pales in comparison to HM) so it wouldn't be as good as ML-like FP.

Pattern matching is a feature of pure functional code rather than a requirement (As useful as it is, every time I touch haskell for fun I always miss the mathematical approach to coding when I then write in C-land).

Enforced purity is a feature, however. That's what I was referring to. However, ..., there is no pure-IO so it would be like Haskell before Monadic IO was figured out (I assume).
I always explain it using recommendation engines. You buy a vacuum and you get suggestions for 10 vacuums you might want to get next. Not so good. You buy a film with Tom Cruise, and you see 10 other Tom Cruise moves suggested, thats not so bad.
Yup, I totally want that. I want a phone that will last 5 years or longer... ideally about 10 years, like the old ones used to.
More like:

Police: "We have a warrant for your apartment, let us in"

Suspect: "Sorry, I lost the key when I went hiking in the Rocky Mountains, there's no way in. Oh, and be aware that if you try to force your way in more than 5 times, the apartment will catch fire and destroy everything inside"

What would happen in this case? Can the suspect be held in contempt?