skysight-inc/HackerNews huggingface dataset:
I miss the old web, because we had vision and dreams for grander technology back then.

Bolted on design took a front seat, but it shouldn't have been our focus.

Open-ended CSS enabled us to reinvent styling and designs over and over and over. We've spent countless hours as a species grappling with how to present information, and how to reinvent the wheel. (Every brand needs to feel special, every company needs a design system.)

If these hours had been spent on semantics and reusability, we might have arrived at a different future. Perhaps rich document sharing rather than a web that's about who can have the fanciest scrolling upvote attention grabbers.

There were some bold ideas in the semantic web, microformats, RSS/RDF. Imagine sharing news and articles like P2P, insightful comments being ranked and scored, interest graphs being cultivated to better you rather than get you to like/subscribe. Platforms as an open and extensible standard.

CSS, meanwhile, is a tool that's being used to position a smiling alien creature that tells you to log into the mobile version.

We focused on the wrong things and evolved in the wrong direction. Shiny and flashy distracted us from rigor and enlightenment.
All of it is completely irrelevant unnecessary complexity. Learn to use Tinkerpop.
Static typing is generally a good thing…I thought this was common sense.

Abstractions are very powerful, but when many people work on a codebase, keeping extra checks via static typing imo is good. Unless your Dev team is _highly_ experienced, then you can put away with the training wheels
And even if you don't want to normalize, at least don't make the DB basically incomprehensible.

Speaking from experience, a "abnormalized" db sucks. https://news.ycombinator.com/item?id=27842820
> Well, many people have had issues with unions creating an environment where most employees 'soldier' (work slowly and uncreatively), by protecting the unproductive, and preventing the productive from being rewarded.

What union has prevented an employer from raising an employees salary? I find it hard to believe that any union has ever done that.

> In cases where domestic companies are protected, the unions tend to try acting as a cartel and raising the whole industry's cost structure (e.g. auto manufacturing 1940-1970).

Germany has much stronger unions than the US. Especially in the automotive industry and German car makers doesn't seem to be doing that badly.
Go's interfaces are a great example.
I'm sorry your startups didn't work out. It sounds like those startups didn't build on your interesting tech ideas (why not?). Did you learn where you went wrong? I'm working on a startup to help people with problems like that, CxO Industries [1].

[1]: https://cxo.industries.
It's nice. Windows only? (I mostly use a Mac at home).

EDIT: no, it's Win/Mac/Linux, apologies...
And probably learning where and how to find information you need.
For me the question isn't if there will be warm bodies around, but if they will have agency, dignity, a longing for justice and a capability for empathy, plus a lot of other things at least I associate with humans being human, rather than appendages of machinery that accumulates power without any use for it other than accumulating more power.
Whether it makes to 100k miles is not the metric.

The metric is, how long before you have to get it to a mechanic to fix a component failure, and how difficult/expensive it is. Engine durability is good in ICE cars these days - it's everything else that falls apart much quicker.

This is completely anecdotal and could be explainable by survivorship bias, but in my experience, past 1990 or so, the newer the car is, the more likely it is to cause regular and expensive maintenance burden on the owner.

Also, think of it this way: people are already used to having to do some serious maintenance work on their cars around 100k miles - why would EV manufacturers not want to eventually target similar repair schedule? In complex projects like these, reliability is a controlled variable.
I am using spring hibernate. It's so powerful. I don't need to write and understand SQL anymore.
Sarcasm off: I see more and more juniors without SQL skills. Various reasons they give me. From the nosql plague to some cloud solutions to the above example. SQL seems to be not so fun anymore. I have a hard time understanding that. Since data storage is such a fundamental part of your application. I would even argue that the data structure to some degree influences the application architecture. Specifically if you need performance and security.
At the end of the day Protonmail itself is a company and they have to follow some rules to keep their operations running. If you look at their transparency report you'll see that they have been complying with government request, both local and international since 2017
https://protonmail.com/blog/transparency-report/
At times it might make sense not to use SQL. That is fine. But I think there is a value in learning SQL. Some reasons:

* Learning effort to Reward ratio is good. A substantial syntax is valid for all of the DBs that support SQL.

* Very easy to remember the syntax. I have not used SQL in a long time but I can still write one without much effort (including the nested queries)

* Pareto: About 70-80% of data retrieval use-cases are well covered in SQL syntax (or a combination of multiple queries like union, creating temp table, etc)

* Tooling: Free & commercial tools which connect to multiple data-sources and provide SQL e.g [1]

[1] https://www.jetbrains.com/datagrip/ (I am not associated with jetbrains)
For Makers: BGA? Or Not? – Makerfabs
As the serious worldwide IC shortage recently, there're so many ICs out of stock, many of our customers have to modify the designs to BGA components. So, for makers: BGA? or Not?
It has, ARPANET had Multics servers, https://multicians.org/mx-net.html
We Should Use Joint Guard 360 Thrive?
Joint Guard 360 Reviews Another reason to take Joint Guard 360 Thrive Formula predominantly others is that it least complex incorporates normal concentrates. There aren't any parts internal those containers. Thusly, we comprehend that there aren't anyt any peculiar angle results that would come roughly; excepting any natural unfavorably susceptible response, obviously. The utilization of most straightforward normal concentrates also strategy that the ones following a veggie lover, vegan, or greatest various eating regimens can utilize the Joint Guard 360 with out horrendous around it. The equivalent is going for people who might perhaps avoid sure components for profound reasons; they may inconsistently find something questionable withinside the strategy here.

https://www.bignewsnetwork.com/news/270562125/joint-guard-360-reviews---get-free-trial-is-joint-guard-really-work

https://groups.google.com/g/joint-guard-360-reviews/c/F5yQ8eDcaJI

https://promosimple.com/giveaways/joint-guard-360-reviews-thrive-health-labs-supplement-worth-it/
Visual Studio Code Update 2021
Basic policing is a necessity for a free society, and it's precisely basic policing that the union-aligned left-wing political movements want defunded.

These movements have no problem with their figureheads spending tens of thousands on their own private security attachments [1] or billions of dollars being spent to expand the number of tax enforcers [2] or to bolster policing to protect the political elite. [3]

[1] https://nypost.com/2021/07/31/aoc-has-spent-thousands-on-per...

[2] https://www.wsj.com/articles/biden-to-seek-80-billion-to-bol...

[3] https://greenwald.substack.com/p/the-capitol-police-armed-wi...
I have this page backed up personally on my machine. I love it so dearly, whenever I find myself scrolling through it again I always end up cackling with laughter.
The article is very informative, but its title feels like "Where are the airplanes that flap their wings like birds?"

Bricks aren't very suitable for automatization and 3D printing seems to be quite a lot more promising, even though the current early forms look clumsy.

Printing a wall gives you an ability to leave precisely calculated empty spaces for plumbing, cables, electrical sockets and whatever we are going to need in the future. This is valuable, speeds up the construction process and reduces total dust.
For everyone (like, for example, me) who has never heard these two names before (or not as replacements for SQL at least...) maybe the following might be useful:

https://stackoverflow.com/questions/13824962/neo4j-cypher-vs...
Mtv3.fi
Curious that 99.99% of applications use an SQL database, must just be a lot of really bad developers. Am I so out of touch? No, no, it’s the children who are wrong.
select * from argument a where a.subject like '%sql%'
What a surprising knowledge. I didn't know that printers support parsing PDF or even ASCII. I considered printers only support printer protocols.
The real concern is that this philosophy has terrifying possibilities (even if they're in the fringe), and being associated with powerful and wealthy people like Musk threatens to validate and realize those possibilities.
The Sample: Add some variety to your information diet
I'm having a hard time finding out the physical dimensions of the cards. Can't see anything in the data sheet about that?

I'd like to know how small a configuration with a Notecard + carrier can be?

For sewing into a kids backpack I think it looks like it will be small enough, but in my mind, putting a tracker inside a shoe would be much better. A backpack is easily forgotten or lost somewhere, but shoes tend to stay with the person. However, to put it in a shoe it'd have to be pretty small.
Yeah one should know why it’s important to normalize, and then when they go a different path, it is done consciously and not because they are inexperienced and didn’t really know any better.

Folks out there who don’t want to learn the ins and outs of database theory - please don’t; read up on it, it’s a very important skill & knowledge to have and doesn’t take long to master. It does take a few days, perhaps weeks, for all the ideas to “click” in your head.

Whilst we having many fads in IT, there are certain sound principles of computer science developed over 40-50 years which one should learn :-) Know the rules before you break them!
To be honest, I would leave a place that tries to improve culture. Either the employees carry decent behavior themselves or not. You can enforce it to a degree, but that will never be not toxic.

That said, business environments are most often "clean". That has advantages and disadvantages. But it allows you to work without distraction.
We're currently moving our Druid/Kafka/Spark setup to BigQuery because of how simple SQL is.
Prefab houses are a thing and they aren't exactly rare. People escaping apartments usually complain about neighbors or lack of a garden, not about the floor plan.
> Having a well-defined and predictable boundary between concerns in the system makes each component, and the system as a whole, easier to assess.

Then why are modular cryptosystems (where e.g. the symmetric cipher algorithm is pluggable) a bad idea?
> RSI from typing

Most office jobs don't involve that much typing. You can also buy keyboards with softer switches. (RSI was more common in the days of mechanical typewriters.) Low physical acitivity can be made up for going to the gym after work.

It sounds to me you never did a day of manual labor in your life.
I would say it is best to do both TDD and have a statically typed language with explicit types written down for every variable. The latter mainly for readability. Let us look for a minute at how mathematicians write things. It is like 'let n be a natural number, let f be a function from the reals to the reals and so on...'. It would be very inconvenient if they wrote things like 'let us have some symbols n and f and you will now have to read the rest of the text to try to figure out what they are....'. It is quite telling that in python it now became customary to include a kind of docstrings to document every parameter. However, no automated process is checking these so they may not be true. So then we start using mypy and, voila, there we are again with static type annotations for every parameter. The whole dynamic language thing was just a detour that did not make anything better. They saved the author a few seconds at the cost of the person trying to read the code taking a few minutes to find out what the type of the parameter was. I also think one should use the 'auto' keyword in C++ quite sparingly.
Since when do we account for people’s feelings when deciding to automate something or not?
That was never the goal of UNIX per se, rather the way Dennis and Richtie managed to get hold of funding and management support to keep going at it.

> When the Computing Sciences Research Center wanted to use Unix on a machine larger than the PDP-7, while another department needed a word processor, Thompson and Ritchie added text processing capabilities to Unix and received funding for a PDP-11/20.[5] For the first time in 1970, the Unix operating system was officially named and ran on the PDP-11/20. A text-formatting program called roff and a text editor were added. All three were written in PDP-11/20 assembly language. Bell Labs used this initial text-processing system, consisting of Unix, roff, and the editor, for text processing of patent applications. Roff soon evolved into troff, the first electronic publishing program with full typesetting capability.

https://en.wikipedia.org/wiki/History_of_Unix
That is correct, but an important part of pull requests is that the pull request branch can be deleted afterwards.
You should learn SQL because it's likely to be a very different language to the ones you already know. In SQL you don't tell the DB how to get the data (for loops and pointers) but what the result should look like, and the DB figures out an execution plan. This style is well worth practising and appreciating.
I don’t find it funny. Monsanto had a huge team of high priced lawyers, and all the corrupt junk science they paid for, against this lone nobody and their case was so bad they /still/ lost.
True. Hard to get enough people to work on the non-Newtonian problem when the robot is expensive. Easier to have several of them, and fix any mechanical problem on the robot, when the robot is simple and inexpensive
I also fly 200k a year (pre-Covid). But it's usually a long-haul trip once or twice every week with a mix of shorter hops; not a 3h flight every day.

Mix of an active travel lifestyle, living in hotels full time, and a lot of work meetings, events, and commitments around the world.
I've spent most of my career hoping that something - anything that's better than SQL will come along and replace it. It's like FORTRAN, except FORTRAN has had the decency to stay in use where it's really the best choice. But SQL is out there, like Clippy. "Hey, I see you're collecting some data. SELECT TRUE FROM HELP WHERE COLLECTING_DATA IS TRUE
>2) no one else is trying to use it at the same time.

Printers are fine with accepting jobs from multiple clients and have been for a long time. After all this is pretty much standard practice for any small office without a server.
> The SQL langauge is old, strange, and important.

I've always found it strange that something hasn't replace SQL, particularly for traditional 'web' client/server applications. But SQL is probably the only technology/language that has survived in the past 30 years of my career.

99% of their SQL databases probably don't require transactions and ACID behaviour. There nearly always needs to be a layer to convert the rows into a format for use (blobs of JSON for a front end etc). Complex queries are hard enough to be used as standard interview questions.

I guess the out of the box performance, availability and reliability of SQL databases, that 0.1% of times when you need ACID writes and transactionality, and the (just about) interoperable SQL makes it an easy choice - no one was fired for choosing SQL.
Your numbers are off, you are using 12kW on average, thus 288kWh per day

See also:
2000-watt society

https://en.m.wikipedia.org/wiki/2000-watt_society
What makes Go's interfaces dynamic in nature?
Why are you refering to Austria?
What is MITRE ATT&CK for ICS and how is it transforming ICS cyber-security?
You mean Switzerland, BÜPF is a law in Switzerland.
You are getting doenvoted because it's untrue. So many faang companies using traditional SQL. And for good reasons. Not to say your two examples are bad. They have their own benefit. But don't become the guy who believes in one replacement solution for all without the knowledge of all. It's annoying
The big advantage of UNIX was that AT&T wasn't allowed to sell it, and it was basically free beer available for a symbolic price, then the UNIX V6 annotated book did the rest.

If UNIX was closed source, sold at the same price as the competition, whatever hardware it run on would have not mattered at all.
And ReCaptcha to verify accounts on a "private" service? Really?
IS GP actually saying making LED bulbs is overall lower entropy than making incandescent, or is he throwing shade?
I've setup my iPhone to not display any notifications except for the red circles next to the app icon. I move all Apps that create notifications into a separate folder on the last home screen. That way I never receive interrupting notifications, and I have to proactively check my Whatsapp/Mail etc.
Android hasn't needed any printer plugin to be manually installed for a while now. Since Oreo I believe.

I've printed from my phone to my pi CUPS server. Even Windows 10 understands IPP.
In Hungary we had house templates since the socialism.

(following sites are in Hungarian)

https://kulcsrakesz.hu/tipushazak/

https://hellohaz.hu/tipushazak/

https://www.leier.hu/tipushazak
I see the increase in people wanting to become lawyers as a negative signal about society. It suggests to me that the law is becoming too complex, that people litigate too much, and this complexity and propensity to litigate becomes a cost.

It’s not an entirely thought out hunch on my end but I think it ties in with how complex the tax code is. To me the tax code is needlessly complex. Sure it’ll likely never fit on a single page but does it need to require tombs and be so complex that smart individuals spend time and brain cells finding ways around it to save corporations and the wealthy money instead of working on science or something else that would benefit society?
That's correct, but unless the investigation determined they acted with malice, they should not be explicitly mentioned.
>To be fair, it is generally one queue that is at fault.

Printer drivers run in process as well as the port monitor (for older printers). You might find the situation improves if you use an inbox driver (one that comes with Windows) and/or the standard port monitor.
Not when sharing memory is done over OS IPC mechanisms.

Which is what you want if the application is to be resilient to crashes and exploits from dynamicallly loaded code.
Personally I am using posteo.de which is pretty transparent as to how they comply (and reject) agency requests:

- https://posteo.de/en/site/privacy

- https://posteo.de/en/site/transparency_report

If you are not a heavy email user and/or encrypting anyway, it seems like a good deal.
Nobody else has invented any other declarative language it seems.

Come on aspiring post-docs, do your thing and launch a new programming language.

If MIT can launch Julia someone can launch a language that's not SQL.
Apologies, PB is prime broking. It's where the bank offers trade facilitation services, especially lending, to a hedge fund or family office.
One takeaway from the article, for me, is that some of the rhetoric of longermism by itself has dangerous potentials in society. For example it could be weaponized politically to marginalize groups.
It's pretty strange that articles comparing static vs dynamic rarely mention team work. For example, we work on a feature, several engineers, everyone in their own branch, with always changing requirements and a lot of experimentation of course. From time to time I have to merge their work to the main branch. In PHP it was always an adventure because merge errors and conflicts (including some very silly ones) are often caught too late at runtime after the whole CI/CD cycle, and then you have to go again. Sure there are tests but they don't cover everything (and it's a nuisance to cover 100% including infrastructure layers if you are in the experimentation phase). PHP has linters but they're very slow and complicate the process. Now that we've switched to Go, merging (and generally team work) is a breeze. The compiler catches all problems immediately, our development time is much shorter now as we don't have to go back and forth with runtime errors.
That is a truism everything is eventually going to die - but SQL has been around for longer than just about all development technologies today and probably will be around a lot longer than things that are popular now. I would guess that it will be around when people have move on from React, Gremlin, and Cypher.
Google "balanced power for tube amplifiers" and see how far that rabbit hole goes ...

(And it's not all superstition, and it's not all for tube amps -- it's all in the SNRR of your power stages for every piece of equipment in your sound chain.)
There’s also csvkit.
SQL is useful but we’ve spent decades to abstract it away, because the Java/SQL articulation is always circumvoluted, and juniors do without.

Then they load two tables in Java and join them manually in memory; or they fetch the principal record, and use the getter to retrieve the dependency, so Hibernate does one query per row.

I accuse all ORMs, especially Hibernate, of making it too easy to skip SQL, and I accuse Java of not supporting multiline strings. We have failed, in most languages, at making it easy enough to write SQL yourself. JPA is nice to cache records in memory, but it’s been way more harmful to performance that it became hard to write SQL directly.
There are about 48 million atoms per 18 grams of water.
>It then held the paper halfway through the machine until I sent enough newlines.

That is what a form feed character is for (ASCII 0x0C).
Loved reading this post!
Your raising of your own children is none of my business, but I'm curious: how do you think that being raised while constantly tracked affects the child later on in life?

My personal armchair worry is that it makes them likely to accept a dystopian surveillance society without even considering that it might be problematic.
The closest that many have come to is to develop ORM libraries. LINQ + EntityFramework Core is my favorite.
Few Tips to Validate Your Mobile App Idea
> and the DB figures out an execution plan.

And then you spend the next hour trying to decipher the plan and work out how to get it to do something that isn't insanely slow.
For small telescopes, you can spend more on the mount than on the glass when starting out. A good mount really pays off for long exposures!
10C isn't an absurdly fast charge rate if your battery has very low internal resistance. Drone / RC people have been doing that (and more) for years, as their batteries are often made for 50C+ discharge rates.
Reading the first part of the titles, I thought maybe it is about poor career choices of fashion models...
For simple queries, row adjacency will beat the graph hands down. And RSBMSs are hard to beat for transactional processing.
What do people expect? To break national and international law and expect law enforcement to simply give up? Nothing on the Internet is untraceable if there is enough infrastructure for surveillance. You can hide under layers, but those layers can be peeled back too. Powerful nation states are not going to simply stand by and allow perfect anonymity on the Internet, now that it has become a critical part of daily life.