skysight-inc/HackerNews huggingface dataset:
I have the same rough opinion of ORMs in general and I've never had the occasion to examine it: it was the right choice for our org because there's no way in hell the engineers were going to learn to write good SQL when they could barely write good Python, especially when I'm far from a SQL expert. I was at the time capable of writing good SQL (presumably after a ramp up period), but I doubt my capability to teach it well without significant time investment. The ORM was a path of least resistance thing, providing a simple, easily-comprehensible interface in the language they were already writing.

In the specific context of stuff-is-on-fire, production database changes (I'll reiterate, this place sucked), the fluency of the ORM and its seamlessness with our code was helpful. I don't know much about LINQ, but I gather that the syntax is declarative, which is a perhaps-minor speedbump that would nevertheless have made me less fluent in the specific above-described scenario.

In the general case of engineering, LINQ looks like something I would far prefer.

This isn't a criticism of your comment or anyone else's, but I have to say I'm amused by how all of my responses downthread of my comment are in defense of me being charitable towards more permissive languages (as I said, my bias probably swings solidly the other way, and if I never engineer in a permissive language again, I'll die happy). I kind of assumed it would go the other way, with HN jumping on my comment as elitist or something.
Assuming your mother and yourself each have your own residences, your 2 households own 12 properties. Your situation isn't unique. Investors over the past decade went on a massive buying spree that has reduced the pool of affordable, available homes.

Assuming you put down 20k on the 100k homes, you've returned 500%. That is incredible, but also fairly common story from the past few years. "I made it rich with real estate!" "How?" "Easy, buy at a historically low price."

The word is out, it's not a secret to success anymore. There is a pile of money out there waiting to invest in under-priced homes. This drives prices up! Because of this, a recession will not trigger a home price drop.

Property values will likely remain stable/inflated until something happens to break whatever math it is that keeps investors invested. It's the massive stockpile of homes investors gobbled up in 2009-12 that need to be released back to the market. It is a self-perpetuating cycle, people rent a home because home prices are too high due to investor held inventory. Then investors keep renting their asset out because renters don't graduate to buying.

I could be way off, or have missed something obvious, but I don't think real-estate is going to be the big moneymaker form this recession unless something happens to dramatically increase inventory in places with jobs.
> From my perspective, React is the thing with the problem: it doesn't have great state management for complex tasks / multi-component coordination. What I want to use is something like RxJS to manage such interactions and state, because it gives me a lot of power/control in a relatively easy way. One of the best options out there that I've seen is redux-observable, and thus Redux itself is just the "stuff inside the oreo" gluing React to all my interesting "epics" describing high level functionality in the applications.

The observer pattern is mentioned in the Gang of Four Book[1], published in 1994. JavaScript first appeared in 1995. Observers predate Redux. You don't need Redux to use observers, and in fact there's nothing about React that is incompatible with RxJS.

> It's also the Unix philosophy thing of use tools that "do one thing well" and then chain them together. React does view components rather well, Redux does state management rather well, Redux-Observable does state "interaction" rather well. Chained together they work remarkably well.

Don't sully UNIX philosophy by comparing it to Redux! UNIX is such a different environment from JS space that it's hard to really even compare the two, but at the very least I think we can agree that "Doing one thing well" in UNIX means not creating a bunch of new problems that you need other tools to solve.

[1] https://www.amazon.com/Design-Patterns-Object-Oriented-Addis...
Root cause analysis:

1. Developed world: Profit motive(i.e. greed).

2. Developing world: Profit motive(i.e. greed) and Bureaucracy(greed, but oft times incompetence).

Greed and incompetence are deeply rooted creations of concentrations of economic incentives in the hands of a few. Capitalism and Socialism are just two ways creating those things, just by slightly different routes. One needs true democratization of technology and its distribution to succeed. Its the only reason why the internet is so powerful and empowering.
Hmm in this demo the interface looks exactly like Zapier (automation service).. wonder what relationship they have: https://zapier.com
Wired runs just fine with JS completely disabled. You won't get this, either.

(Support them with a magazine subscription though!)
Nah, spaghetti monolith is much more navigable than ravioli SOA mess.

1) You have tooling.

2) Probably also shared conventions and libraries.

3) Everything is easy to find and run on single dev machine.

And no, monoliths almost never end up that way as long as they're internally modular. Services are just modules with less sharing and more overhead.
True, but why? To gain some Internetpoints?
The Public Domain Is Working Again – No Thanks to Disney
You have obviously never tried to decipher a swift message or been forced to read the ‘handbook’
Salary and wages would be recorded as OpEx, not CapEx, correct?

I would imagine the CapEx growth is from data centers and equipment for GCP
It's a "please disable ad blocker" message
I won't let my devs build a microservice unless we already have two disparate systems (in development or production) that can use it immediately when it's ready (or very shorty thereafter). That rule seems to keep things in check, and everyone knows when they can pitch a microservice, so we don't have to keep justifying why we won't.
Those reagents are like printer ink and the manufacturer makes plenty of money off of them. Also, the whole thing is supposed to be run with sterilized lines and sterilized water.
Concur. I'm always checking underneath the hood 'because' ... but I have not actually come across a case wherein I've had to.

That said - I think the comment is valid. Transpiling is not compiling and we have not choice but to remain vigilant on the JS, of course, it's not that hard, especially with ES6.
Did you read the article? It's entirely dedicated to explaining how they reluctantly arrived at this conclusion.
> I just meant I notice I feel a lot less freedom after initial release.

Well, there's no arguing with that. And it usually doesn't matter if you have 2 or 200000 users, the migration has to be perfect - and automated - anyway :)
Definitely way less than I used to with CoffeeScript in 2011.

Typescript vs Javascript is less problematic today than modern JavaScript vs browser compatible JavaScript.
Try https://i.imgur.com/GzFnA54.png
In other words, a 32GB ECC memory stick has to include an extra 4GB for parity.

That's actually a price I would be willing to pay.
My father's entire life fit inside of this bird's life. He was born after her and died before her.

That's insane.
If it works. You also have huge companies (AAPL, GOOG, AMZN) who are in this market and invest billions as well, but have massive amounts of revenue. Raising $1b for a what, $3b valuation, puts you out of reach of m/a for probably everyone and requires you to get in $300M revenue yearly at some point with huge amounts of growth potential.
jordigh hasn't given support for that claim.
The place where I work uses it for back-end report generation. In my experience, PyPy's claimed speed benefits are very realistic. For most of our code, we get about a 3x speedup. For some areas of code, we get up to a 7x speedup. The only compatibility issues we've run into stemmed from mistakes on our part (e.g. all dicts are effectively OrderedDicts in PyPy, but your code will break in CPython if you rely on that implementation detail).

As a side note, for some reason, it's terrible for pytest — your tests will take literally 100x as long. If you trust PyPy's compatibility, I'd recommend running your tests with CPython even if you run PyPy in production.
As someone trying to do something similar in 5 years (not nearly in the same situation), I'm having a hard time imagining why you would refinance and take money out (and not the opposite, refinance and pay things down or pay off your mortgage completely).

A lot of the things in your post resonated with me, but seeing this in the comments really got me curious about your math.

Good luck with your endeavor!
Reasons to Invest in Tron (TRX)
You can take a walking tour on Google Maps. Really neat.
50,000 Heck*ng Facebook Ad Variants?
That's sort of literally true except that it's hard to predict how code will be used in the future.

For example, I bet that some dude writing an image decoder in the 90's was thinking "it's cool, I don't have to worry about security" because he just knew that his code wasn't going to be remotely exploitable.

Anyway, my original comment was supposed to be as funny as your handle. I guess the humor ended up being just in how seriously folks took it.

The part I'm not joking about is that folks always underestimate the amount of security bugs that will be found in a piece of code in the future, either because the code ends up used in a way that wasn't predicted, or because some really great bug was just waiting for the right kind of genius to uncover it.
This can only be known after the fact.

To complain about "this obvious treatment that obviously works but regulations delayed for 10 years", is as valid as to complain about "this obviously flawed treatment that kills one person out of ten people and killed my husband, because obviously not enough testing was done".

The error in both complains is to assume that the answer was in anyway obvious. It was not. It almost never is.

I agree with you, totally. I just wanted to emphasize that point.
Multiple versions of Python affected by CRLF injection vulnerability
My bone to pick isn't with the scholarship on the particulars of human hunting patterns. It's with the conclusions related to the evolution of intelligence.

There's a tendency to think that human intelligence arose because of a series of serendipitous adaptations that permitted intelligence to blossom--eating marrow, eating meat, having opposable thumbs, bipedalism, complex vocalizations, etc. But every time a researcher tries to differentiate humans along an axis, we later discover that these adaptations are actually quite pervasive.

Tool use, communication, calorie sources, etc... whatever early humans did we eventually find to actually be quite pervasive in the sense of independently arising. Which suggests that none of these alone is any sort of bottleneck to intelligence. And if such adaptations are incrementally available then why is it human intelligence exploded so? What's the bottleneck? The only response, again, is some sort of cosmic serendipity along the whole chain, but that's conclusory without any evidence (i.e. showing the bottleneck that prevents all these other species from continuing down the same path and, most importantly, why humans are uniquely capable of squeezing through these bottlenecks time and again).

The scholarship in the article is interesting and useful, but as it regards intelligence it doesn't even begin to answer the critical questions.
"The project, financed with university and state-municipal bonds, replaces a coal plant that went into service in 1964." Does it really count as a new one if it's just replacing an old one?
Exactly, the interface being general procedure call. Oh wait... ;)
In pre-Internet days, people managed. You would go to stores and buy stuff. Many did so with cash. If you wanted to learn about something, you'd buy a book, go to the library, or subscribe to a magazine (that last one was likely selling your information in those days).

Then came the Internet. Comparing the before and after, the only strong benefit of the Internet is much better and cheaper access to information. Unfortunately, the "cheaper" part means you end up sacrificing something.

I too would like not to be tracked on the Internet. But I'm not going to forget that I did live a life before the Internet, and it was quite a reasonable life. Moreover, that life is by no means obsolete in today's age. You can get most of what you want in the article while still having the Internet. Just don't try to live your whole life (knowledge + purchases) online.
On assumes that there is always room for additional services. And unforeseen conditions.
That's not completely true. For instance the "LiquiBand" brand includes some products that are CA.

http://www.liquiband.com/region/uk/liquiband-product-range-w...
Interesting questions - we haven't actually come across them before so I'm just going on what I learnt from that blog post, and I may not have the greatest appreciation for their specifics.

- Our strategy is to not start with large grocery retailers for the exact reasons they mention. They're slow to implement new tech and slow to change things in stores. Our primary target is mid to large-size speciality retailers, with low conversion rates, where a small change in conversion rate can have a big effect on sales.

- We've honed our camera integration and have made installation easy and fast with existing cameras. Our clients have even done the install themselves before.

- The post talks about the stores needing to actually make use of the data and our plan for this is to help them do the things they change up semi-regularly anyway (product layouts, visual merchandising, window displays)

- With data transfer, we try not to use the stores WiFi if possible, and use 3G dongles instead. We've managed to use new compression algos so we don't use a huge amount of bandwidth
The demo is the Zapier interface.

From the article:

> Some of the companies that built solutions based on the new API during the preview period include Zapier, Netflix, Mailchimp and Final Draft.
You are missing a credentials.json file. This is not the code's fault but your own.

Read the document you linked:
https://developers.google.com/docs/api/quickstart/python

Read directly above and below the giant blue "ENABLE THE GOOGLE DOCS API" button.
Amazon has a policy that they own all the code you write unless you get it signed off by them as a project that is not related to ANY of their businesses. With Amazon being in so many businesses, they will almost certainly deny whatever idea you want to work on because they have something they claim is related.

He could still do it but that is risky as he could get sued later and I have even heard that it can block any future sale until it gets ironed out.
Your intuition is similar in spirit to Feynman's. For n>2, the number of plausible candidates is sparse, whereas for n<=2, there are many plausible candidates.
I think more interesting is that it, and presumably many others, survived so long in the wild of all places. Many species are known to have significantly extended lifespans in captivity compared to the wild, so that alone isn't unusual. What is is that in all that time, the bird has avoided sickness and disease, predation, other natural perils, as well as man-made perils (according to Wikipedia, major man-made threats for the species are fishing, plastic pollution, lead poisoning, and introduced species), and so on. The bird is going on 70 and has never had access to modern healthcare - something unthinkable for modern society.
Let's talk about comp
Ask HN: How do you achieve high-coverage tests for your SPA UI/UX?
In the backend API world you can get away with doing mostly integration tests and unit tests for the service objects and such. Fairly easy and straightforward.

What's the equivalent approach for the frontend SPA?

It's so easy to write fairly comprehensive tests for a backend API, but how do you do the same for your SPA? What's the most straightforward way to do integration-level testing? What's the best way to quickly cover the look, feel, and states?
Why do you think so? Rust is an interesting language in itself, but I don't see why you'd expect a Rust port of CPython to compete with PyPy in terms of performance. It's still, at its core, the CPython architecture.
It's a reasonable rationale decision... for some very specific circumstances.

I'd vote myself for something nuclear if the other options are unavailable but the investment required to make it work is outrageous, especially if it'll be servicing such a small population.
Define long-term. You could just as well say the universe will eventually collapse in on itself and that will cause extinction in the long-term. None of the species during the Permian-Triassic extinction knew about things like nuclear power plants etc.
Indeed, instead projects just fall rather than get refactored.
Yes, I didn't say it was a free lunch. The entirety of my comments here are about how there are pros and cons to every language that manifest in different situations, and things like "ability to go into ugly technical debt for short-term speed boost" being a pro has nothing to do with the claim that it's an unalloyed good, but there are situations that play to its strengths and weaknesses. I hate to be rude, but I'm really not sure how you thought I hadn't already made this point if you had read the thread we're on. If anything, my original comment comes close to saying that static typing is superior, period (though the same caveats apply about different situations requiring different sets of strength and weaknesses).

The obvious example here is that I unquestionably do my personal scripting in Python instead of C++, despite very much enjoying engineering jobs in the latter to those in the former. Different situations, different requirements.
sounds a lot like Eve online set in medieval times. Guild Wars had a similar system where you could choose a faction and battle other factions to win reputation etc but was nowhere as dynamic as you're describing. also kind of sounds like Dynasty Warriors which kicked ass but followed a more traditional set path of battles

all of these are great games and a blend of them would be awesome if you had a clear vision for how to combine them, but would also probably be a massive undertaking

side note, i wouldn't consider anything a true RTS unless it has some type of resource gathering and tech/unit building element to it
Landing Page Examples You Gotta Save for Your Swipe File
I'll tell you what I think about it: I miss games having LAN support instead of expecting me to connect to a server that won't exist in 15 years or will be nigh unusable when I go to a LAN party somewhere with a crap connection.

That's what I miss most from 90s RTSs.
You may find this short article interesting:

https://foreignpolicy.com/2012/12/06/we-were-pirates-too/
We Were Pirates, Too
Why America was the China of the 19th century.
> margins (that are obscene high right now)

https://wccftech.com/apple-iphone-profits-declining/ This article (and everything else I've read online) reports that iPhone profit margins are declining.
Have you tried MobX? If yes - could you share your criticism?

I liked it more than redux, because you can have have simple class implementation and side effects without much hassle. Also TS support and testing is easy.
IGPU AMD ZFS HTPC FTW!
> i wouldn't consider anything a true RTS unless it has some type of resource gathering and tech/unit building element to it

Then you'd be discounting the Myth series, which means you are objectively incorrect.
Hey folks, I helped build Tonic Document Masker. If you have any questions let us know and we'll be happy to answer.
Thoughts on Hyperfocus and Digital Minimalism
Show HN: Google Trends for German Finance News
I think you touched on the problem here, but didn't quite hit the nail on the head. Many problems could be solved by a smart but small team in a pretty simple way, but that doesn't keep lots of people employed. Look at a lot of open-source tools: they're created by one person, or a small team, and when they're done, they're mostly done and that's it; occasionally they'll do a little maintenance work on it, or some small bugfixes or security updates, but overall there's very little work done after the initial release. By contrast, most commercial stuff is hugely complex, and is constantly being rewritten to use new frameworks and other technologies, but this keeps dev teams motivated and employed, and keeps a nearly constant revenue stream coming from customers.

Basically, just solving a problem once isn't going to keep large teams of people employed long-term, so people don't work that way.
Was closing the university explored? (the article doesn’t mention it) Would we have as much compassion for a school opening on a pacific island where everything needed to be transported in...when you could instead move people to civilization instead?

Total enrollment is 10k students. We’re firing up a replacement coal plant, which is not paying for its CO2, mercury, and uranium emission externalities, for 10k students.
PyPy is fantastic. I'm my option, if they achieve to be faster than CPython in all scenarios( I'm thinking in Numpy/Scikit/Pandas CPython C API abuse), and get full Windows support (they do not support multiprocess in Windows), they WILL be the preferred Python Runtime.

Congratulations PyPy team for the great release!
Except that bandages fall off when you're working, especially if you're working on something dirty. Whereas super glue holds a cut shut even if you're covered in oil. Or, if the cut is on a finger, super glue allows you to keep working as if you aren't even cut.
Rust sort of already has this, though implemented in a worse way. They use 0.[major/minor].[minor/patch]. When the library author wants to indicate that their library is stable, they go to 1.0.0 and promise that they'll never make a breaking change.

The problem with that approach is that you never know if a change is major or minor, since many projects use the 0.A.B differently. Even if projects were standardized, you're missing some information compated to A.B.C or A.B.C.D.
So, in your (uninformed, nonlawyerly) opinion, is a NSO grant with 90 day expiration just taking the piss?
Not sure if it's a coincidence but I read a report on BBC how most insects will die/vanish in 100 years except for cockroaches and other insects that thrive on human waste; butterflies, bees and other insects being too fragile for human pollution. Sobering
Plenty of people pair RxJS with React, including PayPal and Netflix. There is nothing precluding you from doing so. What kind of point is this?
Becoming the Trashcan of Ideology
From the article:

Before opting for coal, the school looked into using liquid natural gas, wind and solar, bio-mass and a host of other options. None of them penciled out, said Mike Ruckhaus, a senior project manager at the university.
I haven't bought new RAM lately, but not that long ago it was often much cheaper to buy an old server and outfit it with used ECC DDR3 than to buy equivalent consumer RAM, simply because there wasn't much demand for previous-generation ECC RAM.

Right now DDR4 is fairly new, but as old servers get rotated out I expect a good market for cheap ECC DDR4 sticks that come from used servers but are too small to get reused in new servers. (unregistered/unbuffered is still a problem though)
There was briefly a thing called HSCSD ("high-speed circuit switched data"), which allowed for 14.4k per circuit, and you could make two simultaneous connections to get 28.8k. It was basically ISDN over GSM.

But you paid per minute (twice as much for 28k) and it was swiftly killed off by GPRS.