skysight-inc/HackerNews huggingface dataset:
Low hanging fruit assuming you can afford a decent used car. I bought both of my EVs used for $10k apiece (and will save about half of those amounts in gas and maintenance costs...). I see lots of people driving around very large vehicles which, new or used, they probably don't absolutely require and which have both high upfront costs and high operating costs.

I think you'd have more of a point if most people were driving around subcompact beaters.

And remember the context was about someone who can already afford to fly regularly (potentially even overseas), in which case switching to an electric car--if they even require a car--is almost certainly feasible.
USPIS was Benjamin Franklin's greatest achievement, and yes I know he popularized parmesan cheese in America.
> I think "alcohol" actually means "alcoholic beverage"

You need to read it in context. "Alcohol" is quite adequately defined at Licensing Act (Scotland) 2005 s.2: http://www.legislation.gov.uk/asp/2005/16/section/2

s.147 defines strength: "strength", in relation to alcohol, is to be determined in accordance with section 2 of the Alcoholic Liquor Duties Act 1979 (c. 4), thus "the alcoholic strength of any liquor is the ratio of the volume of the alcohol contained in the liquor to the volume of the liquor (inclusive of the alcohol contained in it)".

It's defined in such terms as that makes it easy to calculate - both strength and volume can be looked up from the label of the alcohol. The average person wouldn't know where to start with centiliters of pure alcohol in the beverage. You don't actually need to know what a unit is to calculate it, but it's 10ml of pure alcohol, or 25ml of a 40% spirit (standard sales amount). It'll be familiar to most UK drinkers.
I think there's often an underlying confusion between different tools and what they are supposed to do.

An ORM - as the acronym says - is helpful to map database records to objects in the system.
The meaning of the acronym already says that an ORM is not really designed for scenarios like aggregations and reporting. Within those contexts, you don't normally reason in terms of list of "objects" and "relationships" between them.

A "SQL builder" gives you a nice programming interface to build and manipulate SQL statements. Manually building complicated SQL strings is tedious, error prone and it makes it hard to reuse the same queries. With a SQL builder instead you can easily add dynamic conditions, joins etc, based on the logic of your application. Think of building a filterable Rest API that needs to support custom fields and operators passed through the URL querystring: concatenating strings would be hard to scale in terms of complexity.
Some people prefers to use templates instead of SQL builder to add conditions, dynamic values, select fields etc. I personally find that this approach is like a crippled version of a proper SQL builder interface. I prefer to use the expressiveness of a real programming language instead of some (awkward?) template engine syntax.

I think the confusion between these two different tools is caused by the fact that in some popular frameworks as Django or Rails you just get to use the ORM, even if behind the scenes the ORM uses some internal query builder.

Other ORMs like SQLAlchemy instead gives you both tools. You can indeed use SQLAlchemy as a ORM and you can also use it directly as a SQL builder when the ORM abstraction doesn't really work.

Normally, if someone tells me that it's better to write SQL queries by concatenating strings, I'd ask them how they'd build a webpage that filters products in the catalog with a series of filters specified by the user (by price, by title, by reviews, sorting, etc.). Try and build that concatenating raw SQL bits, without making a huge mess.

Also, the "just learn SQL" may apply to ORMs, but certainly not to a SQL builder.
I don't get the impression that everyone who says they want to end homelessness means they want to give the homeless homes for nothing to do so.

Many people just don't want to see it on the streets. It's ruining their view and social standing having such riff-raff on the streets of their expensive world-class cities.

But give them homes? Sure, if they include bars and a keyless lock.

That's the impression I get from many Americans. The whole empathic nuanced understanding of homelessness, substance addiction, and mental illness, is a fairly niche perspective and something I only encountered substantially in the SF bay area. And even then, it was mostly just paying lip service to the popular attitude from what I could tell, few actually did anything about the problem.
Right on. Strength to you.
The article gives specific examples of difficulties using an ORM. It would be nice if people advocating ORMs here gave specific examples of how to overcome them.
Felt the same way. I'm not an expert on language by any stretch, but even I know the role of a noun in Latin is determined by its case rather than its position.

Also is 'Merge' a thing? Or has the author just blessed his concept into proper noun-hood? It's not really explained.
This is also tapping into one of the many optimizations you have to know about when using ORMs. Can you "select" 10M rows from a table? Is an object instantiated for each one? If they're lazily created, when are they destroyed, and where is the buffer of rows held, client side or server side? How do you efficiently update each one without incurring a sql statement for each update?

All of these questions require deep knowledge of the inner workings of the ORM, when in SQL, this is a lot more straightforward.
Neither PS nor Xbox are good examples to begin with. They are already DRMed to the brink.

Stadia however is DRM on steroids. So even worse in this sense than other options, especially when you compare it with proper DRM-free stores. I.e. if it comes as a convenience and you can still download the game - then it's fine. But if it comes as "streaming only" option, it's not.
Now this is excellent point which is true in my experience. It gives little ramp up in starting and keep creating speed breakers as development proceeds to handle real complex business scenarios.
This is the model some crowdfunding platforms like Kickstarter work with: they call it "all-or-nothing funding" [1]. They mention the same benefits, reduced risk for backers if the target amount has not been reached.

[1] https://help.kickstarter.com/hc/en-us/articles/115005047893-...
I would argue that such a clear conflict in these two priorities should necessitate having a bespoke separate governmental organization for SIGSEC, so that the NSA can freely focus on SIGINT.
So, I'm considering this, but I really don't see it.

Yes, there's a shared, limited, resource pool. But that's true of any constrained economic resource.

The element of privatised gain / socialised loss is what's missing. Any given entrant has an all-or-nothing proposition. But gains precisely match others losses, assuming a fixed pie.

The marginal/average cost dynamic is a red herring here, so far as ToTC goes.
You have no idea how true this is, try watching the TV over there!
I've found that you need to first understand basic SQL very well. Then once you've mastered the ORM, it can dramatically improve your productivity. But you need to understand both to reason about what you are doing.

ORMs have their place. Simple CRUD microservice? An ORM can help tremendously. Complex reporting system? Probably not the right tool.

Be careful though. I've run into issues where once you're scaled way up and need the ORM to get out of the way, it can be a beast to detangle if you weren't disciplined.
See if you can come up with some goals that will take you multiple lifetimes to achieve. Spiritual goals. Life Purpose.
Just pick something and see how far you can get with it.
Don't just give up, that's not why you designed all this.
"If we don't sell to XYZ someone else will" is not an argument to keep selling to XYZ, unless you already agree with (or are indifferent to) XYZ and their activities.

"XYZ is doing bad things but it'd be even worse if they did bad things less efficiently" is not an argument to keep selling to XYZ, unless you already agree with (or are indifferent to) XYZ and their activities.

Making an organization less efficient, or otherwise slowing an organization down, is not going to single-handedly stop it, but that doesn't make it pointless or counterproductive.

For the concrete example here, you haven't provided evidence that "less efficient" or "slower" applies only (or disproportionately) to activities that stop hurting people rather than activities that hurt people.

Also, you've created a false dichotomy, dismissing the existence of people who agree with portions of a branch of law but disagree with how that law is enforced.
I work a lot with SQL, not at all ORM's. (I'm on the data extraction, modeling, analysis side). So what's the counter argument here, where to ORM's excel?
This article talks about a few factors that have created this crisis: https://www.nakedcapitalism.com/2019/09/the-fed-has-not-cove...

"What were they thinking?" indeed.
Sans battery is pretty a significant change to the controller software, I think you’ll find is a difficulty when talking inexpensive.
It´s going to kill overseas sales for them. Both me and my gf have Huawei phones, but the next phone will be a Xiaomi.

Fortunately the U.S. didn't kill all Chinese manufacturers, Samsung and the rest are overpriced compared to them.
I’m hoping for twisty knobs and flicky switches
Both of you are wrong.

> Another of these apps, Okash, took this logic of stigmatization even further, harvesting users’ contacts and calling bosses, parents, and friends to shame defaulters into repaying.

(emphasis mine)

This has nothing to do with free markets for risk-taking or confidence assessment. If you want markets like these to work well, you build them using information, not shame. Shame is a tool of last resort used by abusive lenders who are too lazy/stupid/corrupt to do their homework.

This is just another bog standard case of powerful actors abusing weaker ones. These lenders are targeting populations who don't have the knowledge or the resources to "correctly" default or file for bankruptcy, or to defend themselves against abuse when they do manage to do it correctly.

If the borrower defaults, the lender is supposed to stop hassling them and write off the loan. There are a whole bunch of other things they can do, but again, those things are not ethical.
I happen to know of several companies doing physics problems that scale poorly across cores that spend far north of that, usually building out small clusters. Then you run 100s of independent simulations since each individual one doesn't really scale.
I'm never going to send retail customers out a payment gateway with someone else's brand/colors/html, mostly because it's just too confusing to introduce more concepts at that critical stage when they're about to actually make the payment

This is one of the concerns we have with SCA. By the nature of the additional authentication steps, they are necessarily hosted off-site in some situations. Handing your customer off to some other service in the middle of your payment flow and hoping they make it back is the only choice you have. It seems likely that this will reduce conversions, just as anything else that lengthens or complicates the payment flow usually does. What we don’t really know yet is how much difference it will make in practice.
Yes you will be.

https://www.opensecrets.org/outsidespending/
> The only ones that are (negatively) affected are ...

Not true. GDPR imposes costs on every company. Specifically there are the legal compliance costs, software compliance costs, support costs, and that's if you're a "good guy."
Consumer Financial Protection Bureau Public Database
I've also heard this proposed as a risk of vaping. You get hooked on nicotine, can no longer afford expensive e-juice and switch to cigarettes. I think it's too early to know if this is the case, but the complete opposite of what vaping promoters try to sell
Is the Mill CPU still happening? Haven't heard about it in a while...
I guess it varies by company culture. If there was a pullup bar installed in the last startup I worked at, I'd still be there. Instead, there was an endless supply of beer so, meh.
I just built a new workstation and went AMD. I'm amazed by the performances. I have a threadripper 1920 and it performs really well under many different loads (compiling, gaming, video editing). It also handles my dev vms very well. Of course this is purely based on my feeling, but I had an i7-9700 before and while I had faster FPS in some games, it was really bad at handling vms.

This is subjective, but I have a really good feeling about AMD, both on CPU and GPU side.

Only thing I could ask is for more open source (open source CPU firmware), but I think this is only a dream.
You do not use lithium ion batteries for seasonal storage. Use something else, or build enough generation for the weakest season.

1/5 of one year of GDP is not unreasonable for a major component of energy infrastructure. It's not going to be built all at once. I can't find the exact numbers for Australia, but the US has a similar GDP, similar use, much cheaper electricity, and pays 6-8% of GDP for energy. That does include more than electricity, but it's all relevant expenditure.

A fraction of 20% of GDP, because it's across many years, is firmly inside the realm of possibility. If we had to double energy costs it would still be feasible, but that's overkill. We need less than that feasible amount to fund all the necessary construction.
Agree with the article - always found ORM’s over-engineered and too opinionated for my liking. I’ll stick to SQL and keep total control thanks.
What are some good rule-of-thumbs for when to use ORM vs SQL?

I have worked with SQLAlchemy and Entity Framework, before and like them, but haven’t been able to find that magical demarcation line for when to go raw SQL.

Does anyone have basic rules they use for determining this? Applicable to MVP or enterprise level products
One of those goals benefits the people with power who are above the NSA. The other provides a benefit to the public at large that few will notice. Which goal do you think is likely to be top priority?
See

https://www.nytimes.com/2019/07/08/technology/tech-companies...

and

https://www.theregister.co.uk/2019/07/02/npm_abandons_settle...
Like this?
https://laravel.com/docs/6.x/eloquent#advanced-subqueries

Seems more like a limitation of particular implementation than a fundamental problem with the pattern.
It is to nihilists. And also to those who seek to disarm others and render them unable to act for their beliefs.

You see, then, the dire trouble we are in as a polity.
They claim an 8 year / 160K km warranty on their battery. But this usually means they claim to have X percent capacity left after this time. E.g. for the BMW i3 it's 70%. But how can a car owner even measure this? How would one go about claiming this warranty if he thinks it degraded too much?
No, snapchat doesn't care, dude.
China is capitalist.
The manual choice of what is low-hanging fruit is a path to failure. Instead, we should just tax the emission of the dangerous substance. So today, we'll do CO2. After a while, we'll include CH4. Then with a total cap on carbon, we allow the market to trade the right to carbon.

This will allow money to flow to the right places.
I've similarly expressed this opinion openly on Twitter and then I was immediately harassed by Tavis Ormandy of Google Project Zero in my DMs with meme-y taunting messages.

It's odd how dismissive some supposedly-serious security researchers are of hardware implant capabilities.
best comment!
In my friend group it was perfectly normal to borrow / lend small sums of money. That is until a point in my life where my friends now have savings.
Strawman argument but I'll try to explain. If we had only 3 countries then 50% would be from Lithuania and 50% from Rest. That is equal and fair because it doesn't discriminate against anything about those two countries. Mass emigration (to anywhere) is not something we should promote as a good thing. If we take all of the top people in the country that leaves the country poorer and worse off than if we did nothing at all.

The point is just because a place like India has a huge population shouldn't prevent or make it more difficult for people to immigrate from Australia, Europe, Africa, Japan, South Korea, or any less populated countries. The same goes with China. What gives China and India other than population alone the upper hand? Are they somehow more valuable than someone from Japan? Are the more valuable than people throughout Africa?

If you want unbiased immigration you treat everything equal. From within those pools you can argue who is more worth the green card via a merit system that can be scrutinized against those peers within the same country. By your standard India and China would dominate the immigrant population and leave less well off countries with an even worse chance for economic prosperity.
Care to elaborate on which aspect noted above is adverse from your perspective? I would be happy to provide more context and explain in more detail some of the reasoning involved in our decisions.
It's not that simple. For example, this would break my accessibility Chrome Extension that lets users browse just using their voice (https://www.lipsurf.com)
Question: If it makes sense for games to be resalable then why not tickets for cinema or concerts? Ianal afaik both are contractual agreements.
The motivation post for why they created it is a good read: https://www.gabrieladorf.com/palettteapp/
It is almost certainly someone using lazy-loading when they should have disabled it for that query.

Though... since it sounds like the query was returning the entire table at once eager loading will cause issues of another variety at some point.

Either way, I'd chalk it up to bad design rather than bad tools.
To my memory it wasn’t really long ago 1.0 was released.

And.... 5 years flew by apparently
Disappointed? No, I'm not naive.

But if I used Puppet I'd be just as ripshit and hold them to the same standards.
> ORMs are hard for a reason.

Yes, the object-relational impedance mismatch. It's the classic case of having a hammer (OOP) and trying to make everything look like a nail.
Well, my assertion for why people dislike usury isn't because of just high rates, but high rates + unreasonable measures to ensure repayment. Focusing the discussion to whether the rates are a particular economically justified number or not ignores the social aspects of usury.

Even the article doesn't just focus on high interest rates, but discusses hectoring people during their daily lives, calling bosses, friends, and family to shame them into repaying, and linking credit ratings to job applications.

Maybe the outrage on usury would be lower if it was legislated that lenders cannot use public shaming, criminal sanctions, or garnishing wages to force repayment on someone that has stated their intent to default on their loans. The borrower would be blacklisted from the lender in the future and overall interest rates would go higher due to less recovered funds. However, there may be less outrage because as I stated, the key issue isn't just rates but rates + unreasonable lender behavior. The difference between a bank and a loan shark isn't just different rates, but that a bank will only downgrade your credit rating in a default while a loan shark will break your legs.

If you're interested in some reading, check out David Graeber's "Debt: The First 5000 Years." It's a pretty interesting presentation of the social nature of money beyond just a number on a balance sheet.
Was not aware of Grails before. Will check it out.
This should be the top comments, thanks for taking the time to write it out
> Just because a job is simple doesn't mean it doesn't take time & effort

See digging.
Interesting bit from the prompt in iOS 13.

> "Walk around several feet and move your iPhone up and down until a balloon comes into view,"

Existing ultra wideband (eg Decawave) requires several "anchors" to triangulate the location of the tag. I wonder if Apple has built some way to locate the tag with its single anchor (the phone). Perhaps estimating the phones location as it moves up and down via accelerometer.
How to Overcome Imposter Syndrome as a Programmer
Unlikely. Most small time stuff won’t ever be reported properly like that.
You are right about the problems of the existing e-book systems but going back towards felling of trees isn't the right solution. It is possible to build resilience and redundancy on web, either through open source or with a distributed design, and this is something a new player will have to bear in mind while building a replacement.
> Part of why the change couldn’t be enabled by default is because various high performance programs, notably various JavaScript engines and LuaJIT, use this repurposing trick to pack some extra data into pointers.

Does any one know if this sentence can be backed up by a citation?

I know that the NaN-tagging trick assumes that pointers have 48 bits (small enough to fit inside a floating point mantissa), but was this ever a factor for deciding whether 5-level page tables should be added to the Linux kernel or not?
> That's dubious and far more benign than the consequences of a world with climate change.

I'd rather have a connected world with climate change than a disconnected world with WW3... (and probably still climate change, because war is great for CO2 emissions)

For that matter, how many people will care about the Great Barrier Reef (etc) if there's no possibility of them ever being able to travel there?
The first step in recovery is admitting you have a problem!
I didn't think the idea that books would die to be all that widely help of an opinion. So it's a pretty easy argument to agree with. Change? sure. Adapt to new reading habits mediated by technology? Yep. Incorporate features made possible in the digital realm? That too. Die? No.
I do this to myself too but I've gotten better at it. The longer I take to do something, the more I feel it has to have to show as being worthwhile, and that feeds back poorly.

I'm pretty sure orgs also have this problem.
Running raw user SQL isn't a prerequisite of an ORM needed to make it an "ORM", it's a useful feature that most ORMs try to include because the authors recognize the many shortcomings. Also, by writing raw engine-specific SQL, you automatically invalidate one of ORMs biggest selling points which is being SQL-database agnostic.

And by "drop into", this typically means writing custom stitching code that stitches the SQL cursor results back into the models again. It's rarely straightforward.
Yes but it wasn't a (if not amd). It was a series of checks based on specific families of Intel cpus, such as haswell, sandy bridge, etc. So it was never actually querying whether the cpu supported instruction x, it was asking what family it belonged to and then applying static rules based on that. Maybe nuance, but it also has the potential to hurt their processors if not kept up on so maybe less malice and more convenience?
Nope. Even the amount that was here wasn't needed.
Uhm... got a link?

According to [1] it is required and there's no other (documented) way to do it.

Ditto for stripe.createToken() [2].

In fact, there's no word in the docs on how to feed raw card data into the v3 at all.

So we had no choice but to use Stripe.card.createToken() from the v2, but then also use stripe.handleCardAction() from the v3 for confirmation... it's a mess. What did we miss?

[1] https://stripe.com/docs/stripe-js/reference#stripe-create-pa...

[2] https://stripe.com/docs/stripe-js/reference#stripe-create-to...