skysight-inc/HackerNews huggingface dataset:
Caesar's bridges over the Rhine absolutely blew my mind. It's an incredible example of military engineering yielding a tremendous advantage. The military handbooks from throughout the full history of the empire also speak maybe less to engineering specifically, but to the advantages of a literate culture in war. The Romans faced many types of opponents over the centuries, many of which they did not have a natural advantage against, in terms of armament. But they did have tremendous amounts of research and strategy, applicable to all sorts of conditions and opponents. And also impressive skills in logistics.

When it comes to the a Rhine, it's a mistake to think that the Romans were simply more civilized than the Germanic people. That may have been true at one point in time, but over time, the societies on the borders of the empire gained quite a bit of sophistication. The borders were also porous, and the "barbarians" spent years of their lives in the Roman world. This is a big reason the power vacuum created by the collapse of Roman authority was readily filled by "barbarian" kings. The Anglo-Saxons, Franks, Arabs, and Vikings didn't come out of nowhere.

What was lost in the west was institutional complexity. Although it's interesting that the Arabs founded empires that did match Rome in this regard. At least until the Mongols came smashing in.

https://en.m.wikipedia.org/wiki/Caesar%27s_Rhine_bridges
After reading this article I clicked the “discuss on hacker news” link. It led me to this thread [0] with ample discussion.

[0] https://news.ycombinator.com/item?id=6205540
What are you talking about? Enforcement of law is handled by the DOJ.
What is your opinion on abstractions on top of SQL queries?

On paper, a more expressive language that spits out SQL queries sounds great, but I've never seen a single one not become a pain in the ass to use.
I don't have a lot of experience writing Lisp-y code, so perhaps I'm speaking from ignorance, but I think there is a reason that syntax never gained huge traction. Imho a syntax that's concise and expressive is important for effective coding. Having operators for the most common operations is just a small complication that yields a big reward.

Having said that, the amount of keywords and operators that you see in Preql right now, isn't likely to grow by much. I have the basic and common operators covered, and for the most part, the rest can be done with regular functions.

I agree about introspection, which is why in Preql you can ask for the type of any value, list the columns of a table, get the resulting SQL of an expression as a string, and so on. And certainly more can and should be done towards that.
The British Empire lacked one thing that was abundant in the Roman Empire - lumber - and Britain needed lumber, the heat source, more, both because Britain is colder (residential heating) but also because of high demand for charcoal needed to fire blast furnaces to smelt iron.

It was for this reason that Britain began mining coal at scale (as well as harvesting peat), and found herself in need of an efficient way to de-water her mines.

And when the prerequisites (metallurgy, abundant fuel, and economic necessity) converged, the steam engine emerged.
> A language shapes your identity because it literally gives the grammar to your thoughts.

So does your 'identity' (whatever that is) change half way through the sentence. In you head?

Are you literally a different person at either end of your sentence?

SMH.
My accountant working for respected accounting firm in my state literally told me to do this. I've spoken with others, and this is the exact advice they give to S-Corp clients.

I pay myself a "salary" of $60k and the rest (~$240k) is dividends. I pay my taxes quarterly too.
I'm sorry, but I disagree. The codebases I work on are basically Haskell in disguise and that's how I like it. It has absolutely nothing to do with being clever; on the contrary, going all in on FP makes it much harder for us to get away with the dumb mistakes we all inevitably make from time to time. That stability is totally worth learning a few extra concepts for.

> it makes hiring much harder

I don't think this is a real problem. It's disappointing that so much of the industry refuses to train people up on stuff. Hire friendly and open-minded people, sit next to them, and it'll work itself out. I'm a dumb guy who was taken on with no Scala experience and our senior devs just walked me through it. If the modules are written well, you can usually get started working on small improvements without touching monad transformers or whatever.
To me, the downside of graph db is the non-standardized query language.

I tried Gremlin but it feels like an imperative DSL. Cypher queries are more readable, but are limited to Neo4J. I am looking forward for Open Cypher or maybe a variation of Facebook GraphQL.
Building an Indie Product to Compete Against a VC Backed Giant
No-Self or Not-Self?
Down and Out by Ken Wharton?

https://eandt.theiet.org/content/articles/2017/02/science-fi...
Huh? At no point did I read OP as claiming the comic "exhibits" privilege; of fucking course it exposes (by ridiculing) it.

You now appear to be in violent agreement with them, and the misunderstanding seems to be mainly on your side.
Because it’s assumed those private methods’ usage happens within public methods, which should be tested. By testing the public methods and all of its use cases you are also testing private ones. That way you can arbitrarily modify private methods without touching the tests (presuming you’re refactoring and don’t need to modify behavior).
There are probably a few of us who simply disagree. The fact that there aren’t libraries for SQL is a huge advantage in my book, and I say that as someone who’s overseen his developers move more and more from C# to Python because it has libraries that are simply easier to work with.

In this you might be able to guess my objection to many of OPs points. Because the key thing we look for when we decide to implement tech isn’t how good it is, but how easy it is to work with and more importantly, how easy it is to find other people who can pick up when someone’s career take them forward in life.

SQL is the one technology that has been stable enough over the years that no matter who we hire, we can always count on them being capable of working with our Databases. Yes, some of the more expansive functions, especially some of the recursive ones, take a little time to get accustomed to and there will always be some back-and-forth preferences in regards to stores procedures, but on a whole, it’s the one technology that never causes us any pain and never requires retraining.

I’m sure it’s not efficient, and OP is completely correct about the parts about the untapped potential, and I fully support people developing rational alternatives to SQL, I’m simply pointing out why SQL has been the power horse it has since, well basically, since we moved beyond punch cards and why it’ll likely still be so in 50 years.

Because at the end of the day, technology doesn’t really matter to the business. Cost vs benefit does, and as long as it’s easier and therefor cheaper to have people work with SQL (in the big picture), it’ll be what businesses work with.

The only reason you don’t see something similar in declarative programming (or even functional) is really beyond me but it probably has to do with how things evolved and how much easier it is to change that part of the tech stack compared to your databases. If we get a new hire who can do magic with JavaScript/Python/whatever we may consider allowing him/her to do that. We don’t want to, again because the big picture is easier to manage with fewer technologies, but it’s much easier to justify the cost-benefit of that compared to someone wanting to use a different database than the one in our managed cluster. Already you need more staff than that person to maintain it, as developers don’t run database server operations, aren’t part of the contingency staff and so on.

Like I said, I fully encourage the direction OP wants to go. Enterprise rarely invent things, we’d be happy with ball frames if that’s what made us the most money, so we need people like OP to invent things for us to adopt.
I’ve been living in France for the last year. What I don’t understand is how you can be productive with those very long lunch breaks that are common here. If I have a break longer than about 30 minutes, I lose all focus and momentum.

Fortunately, I work from home at my own schedule, and I can usually have a quick lunch alone at my desk.
Dating from the iPhone release makes sense in the "It took a generational new form of computing (mobile)" context.
I block all 3rd party scripts on my browser. The FSF has a patched version of Firefox called Icecat that's set up to do this easily.
is there? ive never seen that hutton on any repos at work.
If you look at age adjusted percentiles, 1% income is much lower than $750K/yr. 30 yr olds making $350k/ are 1%ers, and when they reach 40 or 50 they have substantial investment gains bolstering their compensation.
Tesla owner gets coal-rolled by truck in dangerous incident caught on dashcam
Tech companies have IC promotions.
The difference being that SQL is a standard that's used across many products, has a very flat learning curve, and will be familiar to anyone who uses databases. Whereas Blenders UI is unlike anything else and has a very steep learning curve even for people familiar with other 3D modelling tools.
Show HN: A NLog target for MS Teams channel
A NLog target that write log to Microsoft Teams channel via O365 Webhook Connector.
The frustrating thing is that it's cheaper at that point to run a Linode or Do instance for $5/mo where you get full logs than to pay $9/mo for Netlify analytics.

It's not a perfect comparison but I am still on the lookout for the cheapest way to host a static site while retaining access to access logs.
The iPhone is the relevant reference because it's the reason why ARM is relevant in general-purpose computing today, and e.g. MIPS or POWER aren't
SQL and the relational model mostly works well and it's probably not practical to redo the enormous amount of work that was invested in SQL and its implementations and extensions.

As someone who frequently used SQL for analytics and less frequently for app development, I would gladly use a language that would transparently translate to SQL while adding some syntactic niceties, like Coffeescript did to JS:

- Join / subquery / CTE shortcuts for common use cases (e. g. for the FK lookups that are mentioned in the article)

- More flexible treatment of whitespace (e. g. allow trailing commas, allow reordering of clauses etc.)

And for the language to be usable, it would probably need:
- First class support for some extended SQL syntax commonly used in practice (e.g. Postgres's additions)

- integration with console tools (e.g. psql), common libraries (e.g. pandas, psycopg2) and schema introspection tools

- editor support / syntax highlighting.

It would probably be good to model the syntax of that language on some DSL-friendly general purpose language (like Scala, Kotlin or Ruby).
> ”And yet, the whole community switched pretty quickly.”

This is only true for hobbyists and indie/startup developers. The largest and most popular iOS apps remain Obj-C (with a lot of C++ and in-house frameworks in the mix). There’s no incentive to rewrite something like the Facebook app in Swift.
Haha, in fact I believe js (vanilla, not framework of the week) is probably as durable as SQL
Radio Frequency Skin Effect Burns from Antenna at 1.270 Megahertz [video]
AIeyes: Walking simulator where the world is seen through a realtime neural net
No, we’re factoring in the market impact of the Acorn Archimedes on the wider desktop computing ecosystem compared to the impacts we’re seeing now around ARM on the server and the iMac of M1 based desktop and laptop machines.
25 Gigabit Linux internet router PC build
I wonder if CNN deciding to do coupons was at the same time they gave up on doing news.

https://coupons.cnn.com/
Libelous material is typically presented as fact.
Literally nobody wants taxis in the US.

When I first moved to NYC Uber wasn't really a thing so had to take cabs at times. Even in Manhattan it sucked in so many ways. Examples include:

- The stupid in-car advertising you had to turn off

- Cab card readers seemed to be a common method of skimming

- Getting a cab around shift changes

- Tricks to get a cab to go to somewhere they didn't want to go (ie anywhere that isn't Manhattan below 96th).

- Language barrier. The number of times I've had 14th mistaken for 40th was unbelievable.

- Just the general friction of the interaction and payment.

- Cab cleanliness.

- Inability to call for a cab or schedule one. I came from Australia and was honestly perplexed by this at first.

Years ago I took a few cabs in SF and used to joke with people that the interaction went something like:

"Take me to the end of the street"

"That'll be $30"

I once caught a cab from SFO to Mountain View, which is outside their normal range so there was a 50% surcharge. The guy made many mistakes in just getting off 101 onto 85. Missing exits, going around, that sort of thing. I had to give directions from my phone. The thing turned into $130 since he was running the meter the whole time. I ended up giving him no tip for this on principle even though it was being expensed and he yelled at me. As a cab drive if you can't handle "101 South to 85 South to El Camino North" then you have a problem.

I'm still skeptical about surge pricing in general. I'm not convinced it has much if anything to do with demand vs supply or that drivers see any of it.

But a more interesting story might be how surge pricing has changed in SF over time. For example: does it occur more often? Why? Are less drivers driving? Why?

Recently I tried to use Uber Eats in Miami and it was literally impossible. Why? "No drivers available". Basically no one drove for Uber Eats. They all drove for DoorDash, Seamless/Grubhub or Postmates instead.
Need to Fit Billions of Transistors on a Chip? Let AI Do It
A Moderate Proposal for Radically Better AI-Powered Web Search
>That is pretty clearly contrary to the basics of the relational model itself

The consensus among relational theorists appears to be that data types can be arbitrarily complex. For instance, C.J Date and Hugh Darwen write the following ([1] page 56):

Third, we remind you that types are not limited to simple things like integers. Indeed, we saw in Chapter 1 that values and variables can be arbitrarily complex—and that is so precisely because the types of those values and variables can be arbitrarily complex. Thus, to paraphrase a remark from that chapter, a type might consist of geometric points, or polygons, or X rays, or XML documents, or fingerprints, or arrays, or stacks, or lists, or relations (and on and on).

[1] https://www.dcs.warwick.ac.uk/~hugh/TTM/DTATRM.pdf
We noticed a month ago a few water snails crawling upside down the water surface.
The average age of the female Olympic gymnast is significantly older than the age requirement of the senior elite international gymnast.
https://www.researchgate.net/publication/320508493_CHRONOLOG...
This would be quite problematic with legal writing.
I think it's important to distinguish between what's highly optimizable in theory and what's easily optimizable in practise. The latter working here and now, and the latter being a (possibly perpetual) decade of compiler development away.

An example here is how, sure, in theory, JITs can outpace AOT compilation because they have all the information the AOT compiler has plus runtime insights. But the ability to truly do that always seems to be a decade of compiler development away, with many giving up on the idea entirely.

It's also important to consider what we're comparing SQL's optimizability against. If it's against typical NoSQL databases, most of which seem to favour a lower-level query specification, I can defend SQL's optimizability to the end - with SQL databases having the freedom to dynamically switch algorithms to adapt to the actual contents of the database at the time of the query. Something which, ironically, a stale optimizer hint (i.e. written with the size & shape of the database as it was last year in mind) can actually get in the way of. Not that I'm saying that SQL planners never produce stupid query plans of course.
> I guess the commonality is the end result of homogenizing culture and suppressing cultural diversity for the purposes of political power.

So the native population was obviously suppressed in a bid for political power, but were any other cultures oppressed into homogenizing for the purpose of solidifying someone’s political power? Did someone oppress the Germans to cause them to speak English, or did they assimilate for the obvious economic and social efficiencies? Homogenized culture is the result, but it’s not clear to me that it was nefarious in these cases.
I don't want to get into a debate on the "true scrum", but in my experience non-technical scrum masters/POs/PMs who don't write code (randos in my previous comment) are generally detrimental to the productivity of a development team. Software developers who act as scrum masters and whatnot, while also writing code, are way better.

In my past 10 years of experience (as a tech lead, principal and dev manager), the single change that always increased productivity has been to get rid of PMs/SMs and take over their roles. A brain surgeon coordinates brain surgery, a software developer coordinates software development.
I don't know the answer but with my smartphone I'd rather connect to a website through a VPN running on my own server (with pihole and dns sinkhole), than actually browsing any website directly.
I think it’s simpler than that: wide age gaps in relationships are rare and thus call
attention to themselves. That a culturally significant body of fiction exists to cast negative attention on them (Lolita, American Beauty e.g.) just amplifies the American sense that “this is unusual”. Prejudicial perhaps. But most people choosing where to live and with whom will optimise for familiarity and security. No one is saying we should ban age gaps. Only that they present perceived additional risk once imported from “society in general” to “my living space”.

The usual guidance to “mind your own business” doesn’t really work here because who I live with and where is entirely my business.
By your same logic, a secure operating system would be anti-competitive against malware authors, gas and/or electric heating would be anti-competitive against chimney sweeps, and electric cards would be anti-competitive against oil companies.
> You've mentioned specific details which would make it very easy to identify you

Not in a dysfunctional bureaucracy!

If he was so easily identifiable, they wouldn't have disabled his remote access, hah!
I have not worked in software development but I do work in healthcare. At least in my country, management of hospitals has largely been taken away from healthcare professionals and given to career managers whose background is usually administration, HR or finance. They largely display the same irritating traits as you describe and increasingly interfere in clinical decision making while remaining largely unaccountable - unlike everyone else who works in healthcare they have no professional standards body.

I think the wider problem is a conflation of administration and leadership and a tendency for healthcare professionals to not be good at the politics that comes with leadership positions.
because a relationship between a teenager and someone in their 30s is seen as 'more likely than not to be exploitative'.

I'd like to see some research to back that claim that over 50% relationships with significant age gap are exploitative.

These two statements are not identical.
Could it not be the fact that you said he was blond, but the way you said it? If it were described as a positive attribute, all those reactions make a little more sense.
I like this (and use it) but it has to be said, the syntax is grim.
No, not complete bollocks.

Learning new languages does add different layers to your personality.

I am native-level fluent in three languages, and have some level of fluency in three more.

Learning a new language opens a complete new door to a new culture, and way of thoughts through books, movies, songs, and so much more.

Even if you don't spend time to learn a culture well, i.e. don't listen to music or read literature, learning a new grammar, and very importantly, new words, do reshape you, and gives you new perspectives and ways of thoughts.
In this case you'd get your logs from CF instead of your origin server.
You missed the point. "__CLASSIC_C__" is not a thing (why they don't use __STDC__? I don't know, they don't seem to know either) and the syntax that they use inside that ifdef is.. not what people mean by classic C. It has been there for years and multiple people have pointed it out but they do not seem to care. The funny thing is that they do know how to use the pre-standard C argument syntax (as in https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules...), it's just that they do not want to fix it for that specific file for some reason.

As for

if (ac > 1000) {
return *av[0];
}
return 0;

I am not really sure what to say.

And then for CHECK_FUNCTION_EXISTS();, there are a few rare compilers that do not throw an error at compile-time if said function does not exist.

Also, I have been told that cmake-generated Makefiles invoke cmake itself, so you can't really generate portable Makefiles with it. In addition to that, I have been told that cmake takes ages to compile.

> meaning that in my code I don't need to do stuff like [0] in my code to detect features

I find that much better honestly.
Multipledispatch: A relatively sane approach to multiple dispatch in Python
It's not unethical to cheat at solitaire. Hot take.
GitHub Gist is exactly made for this!

https://gist.github.com/
Don’t forget relentless Hollywood messaging that parenthood is a waste of time, annoying, expensive or just that endlessly hooking up is empowering.

A lot of the issues you’ve described could be solved by incentives for families to stay geographically close together, and leverage the power of grandparents etc like in generations past.
It was probably Pitfall II, I thought the same as you, but looking around the only arcade game I found was Pitfall II, maybe we played some kind of bootleg but I can't find anything about it either.
A bot does not immediately imply fraud.

If you're processing personal data to detect bots to prevent let's say card fraud, fair enough. If you're processing personal data to detect bots for analytics purposes, this might not fly.

Of course, this assumes someone actually gives a shit about enforcing the GDPR, which is currently not the case.
Google tried something along these lines with Contributor ( https://en.wikipedia.org/wiki/Google_Contributor), which in it's first iteration would bid on your own ad impressions. It wasn't popular, partly because it didn't cover all ads (not every ad goes through a public auction) and partly because it fundamentally cost you money. They later tried another version, which only worked with specific partners but did exclude all ads; it wasn't popular either.

(Disclosure: I work on ads at Google, speaking only for myself)
Maybe we can finally agree kernel level anti cheat is useless and unjustified?
This weird preference on here for Slack interruptions is just another manifestation of generational call vs text divide. It's more about cultural context and personal anxiety than real disruptive effect.
Scientists Have Created a New Bendy and Flexible Form of Ice
AI Text-to-Speech models have accents too