skysight-inc/HackerNews huggingface dataset:
Actualised really needs to distill its message to 10-20 minutes max.

I see 1h 16m and close tab.

I've tried watching in the past: tediously repetitious.
Sailing is a different use case though. For wind turbines it doesn't matter if the wind died down in a single place, if you have them spread over a large area and in multiple sites. It's definitely not guaranteed that a single one will always work, but pretty much guaranteed that the system overall will never stop.
And another very recent discussion which treads on similar ground:

https://news.ycombinator.com/item?id=20872571
I guess I should have dug further than the introduction, thanks for point me further in.
> They are for making manipulating the entities

This is where I disagree. I dislike having a value which is the entity. The basic lesson from relational databases and later data oriented design is that you don't have an entity. All you have are aspects that are related.
It's an "exit intent modal"
That makes some sense for the bank. But a person who doesn't qualify for low rates certainly shouldn't qualify for a high rares loan, as that only raises the risk.
Thanks for the tip on JSP. I will look into it.
They also get cheaper if you only buy the single socket versions (assuming you don't need dual socket). The 7702P (the single socket 64 core) is $4425, or $70/core.
> SQL is very literally a domain-specific language for working with relational data; why would we go so far out of our way to eschew writing code in it?

It is, and all ORMs I know use it under-the-hood. It is the boilerplate code by which SQL is issued to the DB, and results parsed into something usable by the rest of the program that people try to avoid writing over and over.
This doesn't fully make sense to me...

I'm kind of curious about what data the select limit 1 queries were returning that the ORM couldn't get in a single query and had to go back per record. Can you shed any light on this?

ORMs have a degree of flexibility. It's possible to write n+1 queries accidentally, especially for developers who are new to the ORM. It's also often possible to address those issues. Sometimes trivially, sometimes not.

The other thing that comes to mind here is that maybe the query was hitting a non-covering index and that was triggering the lookups? In that case a covering index would have fixed the issue?

Curious about this one...
I know that Chomsky knows about inflectional morphology and so I'm sure that his theory does try to account for it, but I was frustrated that all of the examples here were only about word order. The author said

> Word order is, of course, is far more complex than I’ve shown here. There are languages with very free word order, and even within languages there are many intriguing complexities. However, this idea, that Merge can both combine bits of language, and reuse them, gives us a unified understanding of how the grammar of human languages works.

But none of the examples in this simplified account even gestured at noun case, or at the prospect of expressing subject (or agent) with verb conjugation, or at feature agreement.

Is there a straightforward way to understand why Chomsky thinks that this approach addresses those phenomena?
Interesting history, thanks.

Sorry if this is a silly question but is the "upper" in these examples the most significant bit end of the address then?
I wonder how many anxious NYT workers are going to therapy. No, seriously. All that stuff about "bummed out by the world and their role in it" certainly applies to them as well, plus probably more economic anxiety. We're destroying their business, not the other way around. And they don't get the perks we do either.

People of many occupations are probably seeking out therapy more, for the same reasons. I wouldn't single tech out, unless I happened to be obsessively focused on writing about everything that might be wrong with tech.
Many parents give their children money, but I think its most often just a gift. Other than that, I have never heard of anyone lending more than $100 or so to another person that isn't in their immediate family.
But the whole question of "which payment method do you want to use?" is unnecessary complexity if they're sitting there with a card in their hand. Wouldn't it be better to let the front end service handle that question, and then use the appropriate Stripe APIs in the front end?

The whole revelation of stripe was that if a customer was sitting there with a credit card, they just put it there into the same screen and it was done. It was the other crappy products that forced you out into a merchant gateway then back again

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
Given that switching to renewable energy is already becoming cost-competitive with fossil fuels, while CCS is a pure cost, what makes you think a major investment in CCS is more likely than reducing emissions in the first place?
There's absolutely nothing in this world that has frustrated me more than knowing how to write a query in SQL but, for the life of me, not being able to express it using the ORM syntax.

Since then I keep using ORMs (because mapping the things you pull from the db to actual objects is undoubtedly good) but I write my queries by hand.

I also dislike ORMs that, by default, when you try to access an object you forgot to pull from the db with the query you wrote, automatically generate another query to pull the data instead of erroring out.
Right, seems like most problems are related to the Mac version. Wouldn't know about that, never had any noticable issues on Linux.
iOS 13: Optimized Battery Charging
I've been to a few developer conferences in the UK over the years with "famous names" on the bill. But I don't remember detecting any of the speakers having overly burgeoning egos. In fact I got to speak to a quite a few of these folks at lunch time (most, if not all, ate lunch with the attendees as well), breaks and post conference; and in these encounters so none of these folks made me feel "they were too important" to speak to me.

Sure some of the folks have a certain "showmanship" on stage such as back in the day Don Box (and his bath full of SOAP) and these days Scott Hanselman at NDC or Build. But that's fine, they make what could be a dull presentation highly entertaining and you're learning some stuff as well.

Maybe this is a US thing (seeing as the author seems to be based in the US) or certain types of conferences (WordPress conferences?)?
> Disagree that travel doesn't matter

We know - you already made this point in the parent comment.

> sans airplanes

You've moved the goalposts from 'greatly reduced air travel' to 'sans airplanes'.
I guess I'm extraordinarily "lucky" then. I don't participate in competitions, but I'm often "luckier" than entire teams of people working tirelessly for months. And I charge a lot of money for it.
The thing that makes this non obvious is not just that things take longer than you think, but rather as time goes on you have to adjust your expectation of completion to be longer.

For example, if there is a project that is meant to complete in a week. It has now been two weeks, so one week over budget. Most people would think that finishing the project is right around the corner, but rather the expectation should be that it will take another week or two weeks. If you get to the end of a month, same applies - the expectation should be that it will be another month, not that it is right around the corner.
This is a really long-standing battle between user accessibility and user freedom. Any time a software system or platform or OS allows for people to do whatever they want without restriction, you end up with thousands of compromised systems out there. The alternative, in the past, has been to lock everything down unless users go into some kind of "Advanced" mode or "Developer" mode but then users just get tricked into turning that mode on anyways or more advanced users hand wave those restrictions away for less savvy users without explaining any of the implications.

This is the same pattern that happened with IE where users would install all kinds of toolbars accidentally and then get tons of data stolen or when the first iPhone was jailbroken and everyone wanted all the cool jailbreak features. People would jailbreak the phones of their parents, siblings, relatives, friends, etc. without really every explaining what was happening and what the potential pitfalls of that are.

Now, unfortunately, we're at the same impasse with browser extensions. They're super convenient for most people and are widely used but there's another vector of attack for people that aren't as savvy and don't understand the consequences. Especially when it comes to browsing history, payment data, and passwords, it's so easy to compromise a system now when you can hide it in something like a browser extensions.

The real answer is to do a better job educating people about what everything is but no one wants to do that. More skilled users just want to bitch about what gets taken away from them personally without acknowledging the giant elephant that is ignorance. There is so much advanced technology out there now that people don't even understand the consequences of the most mundane actions.

In my opinion, Apple's trying to do something about that even if it comes at the expense of a few power users losing some conveniences. If their past history is any indicator, they will bring back or improve up on this functionality so that power users get it back somehow but, in the meantime, the bigger and more pressing issue is what takes precedence.
Biofuels are certainly a thing - over 100 billion liters were produced last year [0]. For a while, it looked like there were credible avenues to using algae to produce jet fuel, and there were even test flights. Unfortunately, pumping fuel out of the ground is really, really cheap, and most of these companies went under or pivoted [1] (a gallon of algae-produced omega-3 oil or cooking oil is worth far more than a gallon of algae-produced Jet-A).

[0] https://en.wikipedia.org/wiki/Biofuel

[1] https://www.greentechmedia.com/articles/read/lessons-from-th...
It wasn't just about other employees. I lost my job. I got fired in a shitty way. I lost my income source. I lost a job I love. I lost faith in a company I cared about. I was afraid for the future of the ecosystem and my friends still there (most of them resigned since). It was an emotional moment for me and others. Things can be about others AND you, it's not a zero sum game.

Count for this reply: 9
I mostly agree. But lately I've been using Ecto, and I like the approach. It's mostly an SQL generator. So far it's the sanest approach to ORM I've used.
> - $1 game with $49 infrastructure fixed price that you have to pay on every resale

Why would data storage & data bandwidth be upfront fixed price? Bill on usage.
MS is a trillion dollar company. It has the means to do whatever it wants to do.
Lab is not energy linear, and if you're doing rendering/illumination, you won't want to use Lab (unless you're deliberately trying to stylize). It is designed to be a good model of human color perception, not the physics of light.

Lab color space is good for mixing colors in a way that behaves intuitively. E.g. "what color is 'halfway between' these two other colors?", mixing "paint" digitally, producing pleasing gradients, picking colors or creating palettes.
Note that one property described is not true of all distributions. I've used the exponential distribution to predict completion times before, and the exponential distribution has the simple property that on average completion is always the mean completion time at zero away. I have no idea if this is accurate or not, just that I've found the simplicity convenient. In contrast, for the power law distribution used in the blog post the mean completion time from now increases as time passes. (In both cases, average time from start to finish increases on average as time passes.)

I chose the exponential distribution because it's the maximum entropy distribution for a positive number with known mean: https://en.wikipedia.org/wiki/Maximum_entropy_probability_di...
> iOS 13 uses Optimized Battery Charging to slow the rate of battery aging by reducing the time that your iPhone spends fully charged. Your iPhone uses on-device machine learning to understand your daily charging routine so that it can wait until you need to use your iPhone to finish charging past 80 percent.* Charging in this way reduces the wear on your battery and improves its lifespan. Optimized Battery Charging is active only when your iPhone predicts that it will be connected to a charger for a long period of time. […]

* Information regarding your charging routine is stored only on your iPhone. The information isn't included in backups and isn't shared with Apple.
To me it is more of as Ted Neward describes "ORM is Vietnam of Computer Science"[1]

"Although it may seem trite to say it, Object/Relational Mapping is the Vietnam of Computer Science. It represents a quagmire which starts well, gets more complicated as time passes, and before long entraps its users in a commitment that has no clear demarcation point, no clear win conditions, and no clear exit strategy."

[1] http://blogs.tedneward.com/post/the-vietnam-of-computer-scie...
Maybe it's because the problem isn't directly caused by ORMs but just a very poor usage of ORMs. The same problem would have existed if a loop was written to perform the same query.
Outside Lands, Airbnb Prices, and Rockset’s Geospatial Queries
There's a sensible middle ground here, although I agree with the thrust of the message because using an ORM doesn't obviate the need to learn SQL - something I think a lot of developers forget.

The other extreme from using an ORM "for everything" is using SQL "for everything", either via loads of handwritten ad hoc SQL, or stored procedures, UDFs, views, or a mix of all of these. This is just a different nightmare. And don't be fooled: it really is still a nightmare.

A sensible approach blends use of an ORM with handwritten SQL where needed. In fact most ORMs will allow you to do things like build collections of objects from custom SQL anyway, so there's really no need to shy away from it.

One other thing I'd say: I wouldn't necessarily trust my ORM to adequately design my database for me via a code first approach. It's more work but thinking about the data model and explicitly designing the database often yields better results, and you have more control. Code first is OK for simple stuff, but often even simple stuff becomes complex over time so I tend to shy away from it.
>A simple job might be 3 lines of code in an ORM to update a record. In SQL that will be a lot more code especially if that's wiring up a foreign relationships.

That's not a fair comparison unless you include the time and effort involved in creating your ORM models, before you can even write those 3 lines of ORM code. The effort to construct those models isn't even fully amortized over your project, since it must be maintained through schema migrations.

ORMs are like putting on an exoskeleton to go buy groceries because it will let you carry your bags more easily. In my opinion, the complexity and indirection they introduce for accomplishing simple tasks do not justify their existence in the vast majority of cases.
If property taxes are unplayable then selling the house should net a lot of money. If he really just wants to stay there he could get a reverse mortgage at this point to pay property taxes. Unless he has already dipped into that equity.
They're also chartered to provide information assurance.
Why buy a book when you're limited to the device you can read it on and at the whim of when the company will revoke your license to read it?

Nevermind you're also subject to poor application design. Has anyone tried to read books on Windows and had a decent time? I can't find a single app that keeps track of where I am in ebooks or PDFs and it's terrible.
Think tanks may be more talent-limited...

Zing!
Lessons from Building Node Apps in Docker (2019)
That's how kickstarter works, isn't it?
This is exactly it. Even if a malicious extension gets through, they have access to nothing on the user side. It's not a fair trade off but, in my opinion, it is a worthwhile one.
SiC Market Moves into Overdrive
Large dials are the best. For instance the GE8 Honda fit has 3 huge dials, a lever, and 2 huge buttons that control the climate. It's extremely easy to adjust by touch without looking. https://imgur.com/a/V2yhIi6
My phone sucks (Nokia 8110 4G, where mail conked after the first software upgrade) and working for a bank, which disallows external messaging for regulatory reasons.
ORMs can be nice if you're using the database for a single application in a very conventional CRUD pattern, but that's about it. And that's if you have the luxury of building a new DB to go with your new App. If you find yourself doing anything interesting (ie not just CRUDing single rows by ID) you should not only learn SQL, you really need to become familiar with databases. The promise of ORMs (at least when I first encountered them) was "you're not going to have to do SQL" but in reality, you will.
Fedora CoreOS is intended to eventually provide a suitable replacement for ContainerLinux.

Red Hat ships a variant of RHEL called RHEL CoreOS, but the only way to run it is as part of OpenShift (for instance via https://try.openshift.com) where it is the default OS for machines which are managed as part of the cluster, so it’s not a real ContainerLinux equivalent (which you can run individually).
I don't see anything having to do with union busting, but I'm probably overlooking something.
Composing in this context means that one part of your application (eg the list controller) builds part of a query (the select from) and another part (eg the filter controller) builds another part of the query (the where part) and yet another part of you application (the paginator) alters there where part, adds limits and offset and build another query based on the same filter conditions to calculate the total row count. All that without the different controllers knowing each others in advance. This is not possible without complicated string manipulation or building some not-sql-query-algebra.

Some api like prepared statements (supported by the db itself) for building up complex queries step by step would be nice. Does something like this exist?
From what I've seen the beer is manly culture is going away. There's also a lot more awareness of drinking levels and sobriety. It's far easier and more socially acceptable to drink moderately now. These changes are mostly driven by healthy living concerns.

Educating people about lifestyle is proving effective.
Ah, Java. Tooting my own horn a bit, I wrote a custom YAML/XML/JSON parser for C# specifically because the existing parsers required me to turn the data into objects before being able to anything at all, rather than allowing me to interact with the data just as data. Say, cleaning up and/or validating the data.

This is a common problem I've run into in strongly typed languages; can't "just have some data", have to have an object :/

https://www.newtonsoft.com/json vs https://github.com/rangerscience/maptionary
I have to congratulate you for having worked with a quite sophisticated and complex piece of technology for several years and never run into any issues.
I've updated my comment to make clear that's a back-of-the-envelope calculation, and not based on actual performance data. Generally, if you're within a few powers of two with the approach, it's a good start, and empirical data trump rough estimates any day.

The "carbon" vs. "fuel" vs. "CO2 emissions" terminology is legitimate -- these are all different real aspects of the phenomenon. Playing fast and loose between these, or simply confusing the terms (see also kW vs. kWh confusion in energy discussions) is far too common. I specifically called which of these I was using and how they're related.

Much of this would benefit by more use of tables and graphs and sensible comparisons, so that people are at least familiar with appearances. Understanding might or might not follow, but the journalistic practice of "tell a story around numbers without using numbers or pictures" seems to me actively harmful.
My favorite related (not a power law distribution) example of this: life expectancy grows with age.

For some people that's really intuitive and others can use it as a more practical stepping stone on the way to understanding what happens in projects.
This attitude that dumbed-down, 10 second sound-bytes can suffice to examine and grok the nuance and existential dimensionality of the deep topics that he covers is what has lead to such pervading pollution of the information ecology. I would posit to you that you don't have time for shorter videos on these topics, and if you believe that, you will waste your life at a very low-level of communication and awareness around these topics in your attempts at a shortcut to wisdom.
Does that sound wise?
If it seems repetitious I would see if you can find the subtle differences between what occurs to you as mere repetition.

Or am I just witnessing the damage to attention-span of modern living?

There's lots wrong with this attitude IMHO, even though I am guilty of it in many ways I think that you should be able to see the quality of the messages and place them higher than a lot of other information sources that are blasting at you.
Interesting! Is there a simple way to measure memory latency?
That's a load of FUD.

> * I don’t spell well

I don't want to lose minutes or hours debugging a stupid typo.

> * I don’t test much

Writing meaningful tests with my object model without having to care about bizarre SQL semantics.

> * I don’t care how much time and bandwidth it uses

Because ORM will optimize the queries for me, cache results and perform lazy loading when possible.

> * I only know Java (or C#, or whatever)

Using the full power of expressive languages to work with my object models, keep things DRY and reuse code, and have support for different storage engines and sql flavors.
An outsider could perhaps look at capitalism in the same way.
> Major concern I have is that every game will "become a subscription service". I love my stack of steam games sat there to be played whenever I want. This is available as I currently have a perpetual license for them, and this is possible as the current market sells many many many more of these licenses than there are people concurrently playing these games.

Valve tried to argue that Steam is already a subscription service, and failed. I don't see how this ruling will cause any change here other than allow transfer of ownership.
Well, yes, but the problem is that (unlike Dual EC-DRBG) other people can also exploit these things when open. For instance, I suppose, would the USA be better if Project Zero shipped all their stuff to the NSA and they both kept it quiet or would the USA be better if they fixed these things.

The point is to gain differential advantage. When you're the rich guy you don't want everyone's doors to be unlockable. When you're the poor guy you do. The USA is the rich guy.
when the fed writes a check to a bank, the money isn't deducted from an account, it's new money created out of thin air.

when the fed receives a check from a bank, the money doesn't get deposited and stored in some account, the money just stops existing.