skysight-inc/HackerNews huggingface dataset:
My guess is: it doesn't really matter for established companies, because the market isn't actually that competitive. It matters for startups, with the advantage going to in-person (office or apartment) work. Tomorrow's startups become the established companies of the next decade, so eventually the pendulum will swing back toward office work, with lots of executives convinced it brings higher productivity. It's really because of path dependence, though, and not because of any intrinsic merits.

The dirty secret of capitalism is that companies become successful based on what customers do, not what owners or executives or employees do. A product or service basically just has to work, just enough that the transaction still happens. The amount of money the company makes depends on how many customers it has and how much it charges each one, not on how good its product is, so long as the product is "good enough". When the company is young and scrambling to take the market, then maybe effort and efficiency matters, so that you can go from "not good enough" to "good enough" faster than anyone else. But once you're already way past "good enough", you can fire 75% of the company and you'll still continue collecting money until the market changes enough that your product is no longer "good enough".
The latter is the only one of those two whose length you actually know.
I disagree. That no nuance stuff does exactly what you are wanting to avoid.

Aside from that, the law must take into consideration one’s ability to reason because that is the method in which a jury finds facts.. based on reasonability. You wouldn’t convict someone who suffered from a mental handicap to a punishment that was equal to someone who did the same with full faculties, right?
I feel like it would be pretty easy to artificially limit cars to 75mph.

Also I drove a car that took 15 seconds to get to 60 throughout high school and it was fine.

Wearing a motorcycle helmet inside a car does nothing for pedestrians, cyclists, etc. Also I would argue there's a loss of utility because it probably interferes with peripheral vision and messes up your hair. But sure, make people wear a helmet, fine by me. The point is that there's room for easy improvement in car safety, and a helmet counts, I suppose.
At least they aren't regularly flown across the country anymore, thanks to check truncation, i.e. Check 21:

https://www.washingtonpost.com/archive/business/1996/01/17/t...

They still have to move across the country in one direction, though... I'm still not quite over the fact that I need physical access to my mailbox to receive payments from certain entities.
The first Arduinos with that formfactor which supports shields are from around 2005[0]. The Uno wasn't the first[1], it was just a model line set up for that specific formfactor for consistency, since the name was changing frequently (e.g. "Arduino Diecimila", "Arduino Duemilanove", etc).

[0] https://docs.arduino.cc/retired/boards/arduino-serial
[1] https://docs.arduino.cc/retired/other/arduino-older-boards
Good news then, growth in speed for single threaded has been slowing
https://archive.is/ZhVZx
We are in the midsts of the Third Opium War, we just don't call it that yet.
You have to optimize and test constantly for AdWords to pay off (disable content network advertising, geographic targeting on a schedule that follows the sun, a/b testing copy) and build methods of retaining users that don't buy to eventually convert (email newsletters, add us on Facebook, sign-up for this free ebook, blah blah). My guess is small business doesn't have the time to tweak all these things.

There are also small tricks about writing copy to make it economical. Social media sites have the retention mechanics built for you so I'm not surprised they convert better. Just my 2 cents as a guy who does marketing for some spare pocket change.
Maybe it's just luck. I could be in the corner of the room facing the wall, and I'll just attract trouble.
You werent using OSB on walls were you? Which goes back to the moisture thing...
For me it was an old Britannica set that had coloured anatomical drawings on translucent pages so you could peel away the skin and work down to the bones — both sexes.
An ORM is a specific kind of data layer. It is general-purpose, and as the name suggests, it is an Object-Relational Mapper whose primary purpose is to map relations to objects and vice-versa.

So no, bespoke data access layer code is not an ORM.
Car manufacturers never skimped on QC? Take a look at the wonderful Corvair. Or the Pinto.

So much of this is survivor bias or just nostalgia. Some things were better back in the 50s, some weren't. Somethings in the 50's seemed great but in hindsight were pretty bad (asbestos, thalidomide, DDT, aluminum wiring).

And some of the "American Exceptionalism" was also a response to WW2. I know an entire generation who would never buy anything made in Japan because of Pearl Harbor. And I had an uncle who flew in the 8th AF who would go into a rage whenever he saw a VW Beetle on the road. In electronics, Japanese-made used to be a slur, until they dominated electronics.

My first home was a Sears home. It was small but seemed okay for a first home. It had new siding, and the previous owner had replaced the aluminum wiring. I don't know if the plumbing had been replaced, but it was, as most houses are, a House of Theseus.
How is it trademark violation to put up, say, Toyota billboards around the Honda dealership? Advertise the NYT in the Washington Post? Have a big freakin' Coke banner at the end of the soda aisle?

Yes, this kind of advertising is a stupid zero-sum game, but our society in general, and free markets in particular have a lot of stupid zero-sum games. I see no reason why this one should be illegal.
Where the same methods are used a higher quality products does make a significant difference.

Denser growth means it's harder for pests to damage and water to penetrate.

My mom's place is build with high grade fir for every stud and beam and there's clear differences in how it's holding up to contemporaries built using pine from the same era (old growth too). Materials make a difference.
Ask the bot to swear, they don't like doing that
sure, sometimes, rarely -- these are exceptions, not rules

in general, it should not be possible for user input to produce arbitrarily complex queries against your database

each input element in an HTML form should map to a well-defined parameter of a SQL query builder, like, you shouldn't be dynamically composing sub-queries based on the value of a text field, the value should add a where or join or whatever other clause to the single well-defined query

sometimes this isn't possible but these should be super rare exceptions
NO DOUBT, I am lucky to live in central coast and my house is made of it. I think the post a couple up was talking about moisture and rot resistance tho.
Edit: just says old growth ... i thought i saw redwood
South Koreans become one year younger under new age-counting law
My only real ORM experience is with SQLAlchemy (and a tiny bit of trying to learn ecto) and based on this thread I have to ask are all the other ORMs just terrible?

I've been learning some rust lately and writing out boilerplate code to handle simple CRUD is painstaking and it feels like a waste of my time.

SQLAlechemy's ORM can get in the way a bit for more complex queries (or ones you are trying to optimize) but you can always just drop down and write the SQL for those specifically.
CBDC is the worst possible option. This is the fastest way to dystopia having your money expire, getting fined directly from your account for things like JWalking, Etc.
Wood density matters , primarily affected by growing rate, with old growth being denser than these pin stick forests we have now.

Really...
The combination of a bigger remote talent pool and enhanced productivity with AI tools is going to make it pretty rough for mediocre programmers in the medium term, I think.
Right, that's the older generation speaking circuitously about what the Bay Area can do with land use and conveniently landing on the status quo being best-of-all-possible-worlds. The fact is, the city changes anyway.

More and more newcomers in the past two decades ended up with roommates because of rent. E-bikes changed the game with getting over the hills and a lot of families are using them now, pulling kids and groceries despite the lack of infrastructure. Lots of people opt to get things delivered instead of driving down the peninsula to Colma. On the roads themselves, the self-driving taxis are all over the city every day - and mostly they do work, even if "Cruise gets stuck" is a meme; if they expand to achieve the current market share of Uber and Lyft at the projected cost metrics, SF's auto fleet will be majority centralized and professionally-operated. Meanwhile the fastest expanding public transit in the Bay is the ferry system, which in its current incarnation is largely a product of the '89 quake jumpstarting ridership, and now serves as a link to some relatively distant locales. What the whole Bay Area government did - not just SF - is spend a generation kicking cans down roads and letting real estate prices run up, and the time is ripe for a transformation that leverages all the new stuff.

Right now everything, big and small, good and bad, gets challenged by CEQA and affordable unit requirements. It's an excuse for graft to run through City Hall. But the entire west side of the city has ample room to grow. It is not particularly beautiful as it is - it's just row housing. The transit and traffic problem is just geometry, doing more in less space.

The way in which the city streets are currently designed is "every street is a stroad" - garage curb cuts are everywhere, every inch is available for parking, everything on the grid is a thru street. Many of the garages are not used as garages, they are used as rentals. Most of the delays are from intersections along major corridors, not access to destinations. So in practice, the city is subsidizing a lot of street space as a parking lot, which exacerbates the need for cars and car infra. All you have to do to make the kind of transformation Paris has made and go heavier into bike use is to carve out the block into a cul-de-sac with bollards - a stronger version of what's already been experimented with in "Slow Streets" and "Neighborways" since 2020. You don't get a fight over parking and lane space, but the fast thru traffic goes away and it becomes dead easy to set up a few consecutive blocks like that to create bicycle corridors, while reducing delay along the fast corridor by eliminating conflict points.

There's plenty more, but that's basically where I see things going. A lot of changes will be precipitated by self-driving taxis because adoption of those removes the "owner's rights" element of why constituents vote to keep the streets exactly as-is.
> Also, as mentioned in the acquisition FAQ [2], we don't have any plans to change the open-source licensing structure, and we're still open to contributions.

Well, assuming you require contributors to sign a CLA, that is requiring anyone who donates software to your organization to allow you to release it in nonfree products (something Docker requires today, given that they ship proprietary software).

I'm personally really tired of this sort of free software cosplay, where companies pretend to respect user freedoms but are actually just pretending to embrace free software ideology with a license here or there but don't actually support user freedoms (as evidenced by their continued use of nonfree licenses and CLAs to enable dual licensing).

> but so long as you're setting natural (non-contrived) boundaries between open-source and proprietary, then I don't think you're doing anything wrong

I do. You can't be said to respect user freedoms if you, you know, don't respect user freedoms on a regular basis by promoting proprietary software that users can't easily modify and redistribute freely. That's actively user-hostile, just like Docker Inc has been with Docker Desktop and other products.
> It's astounding to me that anyone could believe it's possible to be truly masculine while neutering one's experience of human emotion. Being too afraid of emotion to ever express it, and making your child suffer for your fear, is cowardice, not masculinity.

I did not claim that fathers should be devoid of emotion or neuter their emotion. You added that strawman on your own. This is the 3rd or 4th comment in this thread where someone made a similar claim.

Clearly even in your quote I said "the person a child goes to" as in the person responsible for that. Just because your child does not come to you first for emotional support, does that mean you have to be cold and unapproachable to your child? When did I claim that or why would you assume one extreme or the other?

Why do you people insist that parents should not have specific responsibilities based on their abilities. If you honestly believe you can support your child better than their mother emotionally then take on that role. No problem there. So long as the mother is able to exchange masculine responsibilities with you.

Why do you insist that fathers should be responsible for everything and mothers should do whatever they feel like doing? It sounds to me like 80% of parenting is done by the father according to you.

A son needs someone to teach them how to be strong and manly as well as gentle and kind and intouch with their emotions. Why so you insist thr father should do all these things? Why do you resist havig to share the responsibility with the mother?

This is basic human organizational structure. You can't have the CEO and CFO have the same exact job. You can't have two commanding officers responsible for the same subordinates in the military. Lookup "tyranny of the structureless".

In your attempt to do everything on your own, you rob your child the opportunity to get close to both parents bot worse than that, you rob them of structure and clarity which are essential to healthy development.
Danger is relative, that's normal in Germany.
Submarines and spacecraft.
Does anybody know of something similar but for water quality monitoring?
OK, I think I see the problem with this conversation. When people talk about personality in communication, they generally mean the manner of expression. What you seem to want is a tailoring of the content to your needs. At the moment, I believe the only way to do this is with prompt engineering. I suppose eventually some company will offer the ability to customize your account profile so that responses are better tailored.
An interesting fact is that the ground stop after 9/11 was what prompted that legislation and why remote deposit from a mobile phone or business scanner is possible.

https://www.protocol.com/newsletters/sourcecode/tech-legacy-...

https://www.frbsf.org/education/publications/doctor-econ/201...

https://www.frbsf.org/education/teacher-resources/open-opera...

https://en.wikipedia.org/wiki/Closings_and_cancellations_fol...
I believe this to be the elephant in the room, I wouldn't be surprised if the viewport gave way before the hull.
Are you referring to individual employees or the companies? Clearly many companies are mandating RTO despite remote/self-determined hybrid supported by a strong majority of employee sentiment (and often performance data)
Im imagining a build tool to take raw SQL statements and validate them and produce typescript code from them. So ie const data = query(select * from table_a where pk = x) is a promise of the appropriate type etc. I currently use prisma and it is kind of good but can definitely be leaky and is rough around the edges. I like doing raw SQL statements but making it type safe is annoying.
Because a true threat requires a bunch of things, including a time and an ability, and at least some insinuation of a method. It has to be a real method, so if the person is on the other side of the country and there's no reason to think the person is hiring a hitman (or has a Death Note, hah), it's not a true threat.
> ORMs are an anti-pattern. They are a toy for startups, but eventually hurt more than help.

Does anyone actually say this?
I can't remember, right off. I want to say that slime was having issues for me one day, and someone suggested sly. I switched and inertia has kept me on it. I don't know of that many differences, all told. It was nice that I didn't have to remember what all nice plugins I wanted for the repl. And then the stickers and such are just fun.
I wonder if someone from marketing chimed in on a testing topic, to point out that for most lines of code written today, unit tests and integration tests aren't cost effective, and that companies are wasting billions of dollars on writing and running tests that pass 99% of the time, anyways...
In my opinion a critical part of an AGI is learning on the fly from few examples. Humans do this well.

When humans play (video)games against an AI they will usually find some pattern of behavior that the AI falls into. Once they find it, they can continuously take advantage of this pattern of behavior and abuse it for great success. I think current LLMs still fall into this category. But I think they might be able to handle this relatively well quite soon.
Was waiting for Dapper to get brought up. Fantastic micro ORM.
I did not read fiction until I was in my mid-20s, and Steinbeck's "East of Eden" is what it took me to realize that reading helps develop empathy (particularly fiction, and particularly for us spectrum kiddos) — John won a Nobel Peace Prize for this publication.

In a similar vein, I feel that LLMs are helping me to develop proper "ego destruction" which few others have been smart enough to deal with (me).

Should be an exciting future.
> Ah, the hubris of devs who honestly believe they can whip out a solution in a day that beats a dedicated army of developers singularly focused on the task of large data management, storage, and serialization.

A "dedicated army of developers" who've been "going on 50 years" but whose flagship solutions are still single-point-of-failure, still noncompositional, still untestable, still have bizarre and incomprehensible performance characteristics. Yeah, no, I'm going to do stuff in regular application code, thanks.
> Not only does each ORM have a different API and access pattern to do this

I think it is to be expected that different ORM frameworks would have differing APIs and access patterns. Similar to how different RDBMS's often have differences in the syntaxes and features that they support. It's not a big deal to look up the correct syntax in my opinion.

> you're managing the object model

Which means in the worst case that for some portion of your app you're basically back to where you were if you weren't using an ORM. Although I've found that JPA, for example, plays pretty nicely with native SQL queries (caching gets more difficult, but I think that's to be expected when moving logic out of the app and into the database regardless of whether you are using an ORM or not).

> ALONG WITH custom SQL for migrations

Personally I've always used custom SQL for all migrations. While ORMs often come with a tool to automatically generate a schema, I've never worked on a project that actually used this tool in production.

> There is also non-trivial danger in letting your ORM decide what data types your database schema should use. Got UUIDs? The ORM will store them as strings.

Some data types can be a bit tricky, but any competent ORM should at the very least have hooks to override the type on a field or implement your own custom handlers. [1]

> What you appear to consider "advanced features" are what some others of us consider "perfectly normal." Let's be honest: most devs consider knowing the difference between a LEFT JOIN and an INNER JOIN to be an advanced topic.

I said "more advanced features" - as in more advanced than basic SELECT/INSERT/UPDATE statements. I don't think any feature that you mentioned is particularly challenging to understand. And literally every entry-level developer I've ever hired has easily been able to explain the difference between LEFT and INNER joins in an interview.

[1] https://stackoverflow.com/a/12824827
had a bot do this too
Related: A two-server three-jail network setup (firewall, vlan, tunnels)

https://blog.uidrafter.com/freebsd-jails-network-setup
That's how Zelle works. It's just a front end to ACH with delayed reconciliation while creating the appearance of instant transfers.
Google Chrome and vanilla Chromium have little to distinguish them outside of branding. The difference is not one of repositories but of build flags.

Suggesting Lynx as an alternative clarifies that your remarks are unserious, or you are out of touch with reality --- charitably I will assume the former.
I think ORMs are fine for small queries. For example: User.find_by(email: "xyz"). But as the queries get more complex ORMs fall apart and simply using raw SQL is better imo.
What's the best option?
Personally, this seems extremely tame.
This is from a maintainer of wlroots:

>Maintainer of sway and wlroots here. The Nvidia proprietary driver does not support sway, not the other way around.

>Their standard, EGLStreams, is only implemented by their proprietary drivers, so in order to test that codepath we'd have to use a famously broken and undebuggable driver, which we're not interested in - and make no mistake, we get our hands dirty in the drivers all the time. Their standard also has serious technical problems - lots of really important features simply are not possible to implement based on the proprietary driver. We can't export buffers to clients, overlay planes don't work, buffer presentation timings are impossible... Supporting this driver would be a massive overhaul and would probably make the good drivers worse.

https://news.ycombinator.com/item?id=21628494
Skyrocketing rent demonstrates the strong demand for such environments. Prices would fall if there were more competitive cities.
it's not like stored procedures are inherently faster than normal queries, right?

as long as you're not doing anything dumb like connection-per-request, query caching should work the same
Yep, and there is always a business case for trying to suppress/ignore the new technology and stick with what you know and what has been profitable for many years. This is how once mighty businesses fail. Look at Sears, who was Amazon before anybody knew what the Internet was, but then the Internet appeared and they couldn't move on because they had invested too much in their old business model. Moving a catalog mail order business online should be an incredibly easy transition, but decade after decade they dawdled until it was too late because it would have hurt the stores and the quarterly profits.
Capitalism has stages.
Sounds like return to office mandates correlate with less attrition and easier recruitment…
UBS Preparing to Cut over Half of Credit Suisse Workforce