skysight-inc/HackerNews huggingface dataset:
I would assume 'proper' means 'adequate in terms of function and aesthetics'. maybe something like 'themes that don't eschew real usefulness'.
those themes did exist before solarized, but they were not the norm in many circles (mine included), as many authors did sacrifice function for the look&feel.

solarized demonstrated how to apply colour theory/science to the landscape.

I would add that it has been not just the theme that serves as an example, also the _how to make_ a theme following those principles.
It’s especially unique because the 6502 is not particularly “static,” so single-stepping it is a challenge.
> However, what he fails to realize is the media buyers love to be wined and dined with fancy dinners. If you fire all of your sales staff they will just take their spend to the next company who can take them to five star meals and other cool outings.

Advertising spend doesn't work like pharmaceutical sales. They will renew precisely because they like the ROI, whether they get pampered or not, because as advertising channels, social media platform are additive. If it gives you positive ROI, you're strictly better off advertising on a network than not advertising on it, because the social networks themselves are mutually exclusive in terms of attention. That is, you can't access Twitter's eyeball-seconds any other way than through Twitter.
devopsengineers.slack.com
I mean, if you have one task to do only, multi-tasking is kind of pointless yes
Congrats to the Remix team.

I'm not entirely sure how you acquire a web framework or what the end-goal is, but I'm sure smarter people than I have the done maths.
Maybe you've been more lucky than me, but I've seen plenty of such "junior devs" in positions of influence, with titles such as "senior" or "principal" dev, "architect" or "engineering manager". In many places, titles like that accrue automatically as people get older, especially if they play the political game reasonably well.

Some of them will then happily do what you correctly label "Premature optimization" in the microcode, but proceed to make big mistakes in the overall design that leads to several orders of magnitude slowdowns in the general design.

I believe the problem is in the training. As junior devs, they may have been scolded for premature optimizations of microcode, but worked within a well thought-out design at the macro level. Then they advance in ranks, and have to do the design part as well, but they never learned to think about the performance at that level, something that benefits a lot from some contemplation up front.
Markus Triska Interview on Prolog
It has everything to do with automatic validation on both sides and little to do with the transfer size.
LIKE is case-independent by default. This prevents using an index for optimization, even for LIKE '<prefix>%'. To fix this, you can switch to GLOB '1*', which is case-sensitive, use the NOCASE collating sequence for the index, or use the case_sensitive_like pragma for a more global change.

To show that, here's an example session comparing LIKE and GLOB with and without an index:

[jim@mbp ~]$ sqlite3
-- Loading resources from /Users/jim/.sqliterc
SQLite version 3.38.0 2022-02-22 19:15:21 with the Encryption (see-aes128-ofb)
Copyright 2016 Hipp, Wyrick & Company, Inc.
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> create table t2 (v text);
sqlite> insert into t2 (v) values (1);
sqlite> insert into t2 (v) values ('2');
sqlite> select * from t2 where v like '1%';
v
-
1
sqlite> explain select * from t2 where v like '1%';
addr opcode p1 p2 p3 p4 p5 comment
---- ------------- ---- ---- ---- ------------- -- -------------
0 Init 0 10 0 0
1 OpenRead 0 3 0 1 0
2 Rewind 0 9 0 0
3 Column 0 0 3 0
4 Function 1 2 1 like(2) 0
5 IfNot 1 8 1 0
6 Column 0 0 4 0
7 ResultRow 4 1 0 0
8 Next 0 3 0 1
9 Halt 0 0 0 0
10 Transaction 0 0 2 0 1
11 String8 0 2 0 1% 0
12 Goto 0 1 0 0

GLOB behaves in a similar way because there is no index:

sqlite> explain select * from t2 where v glob '1%';
addr opcode p1 p2 p3 p4 p5 comment
---- ------------- ---- ---- ---- ------------- -- -------------
0 Init 0 10 0 0
1 OpenRead 0 3 0 1 0
2 Rewind 0 9 0 0
3 Column 0 0 3 0
4 Function 1 2 1 glob(2) 0
5 IfNot 1 8 1 0
6 Column 0 0 4 0
7 ResultRow 4 1 0 0
8 Next 0 3 0 1
9 Halt 0 0 0 0
10 Transaction 0 0 2 0 1
11 String8 0 2 0 1% 0
12 Goto 0 1 0 0

Create an index on v and see how things change:

sqlite> create index i2 on t2 (v);
sqlite> explain select * from t2 where v glob '1%';
addr opcode p1 p2 p3 p4 p5 comment
---- ------------- ---- ---- ---- ------------- -- -------------
0 Init 0 15 0 0
1 OpenRead 1 4 0 k(2,,) 0
2 Integer 1 1 0 0
3 String8 0 2 1 1% 0
4 SeekGE 1 13 2 1 0
5 String8 0 2 1 1& 0
6 IdxGE 1 13 2 1 0
7 Column 1 0 5 0
8 Function 1 4 3 glob(2) 0
9 IfNot 3 12 1 0
10 Column 1 0 6 0
11 ResultRow 6 1 0 0
12 Next 1 6 0 0
13 DecrJumpZero 1 3 0 0
14 Halt 0 0 0 0
15 Transaction 0 0 3 0 1
16 String8 0 4 0 1% 0
17 Goto 0 1 0 0
sqlite> explain select * from t2 where v like '1%';
addr opcode p1 p2 p3 p4 p5 comment
---- ------------- ---- ---- ---- ------------- -- -------------
0 Init 0 10 0 0
1 OpenRead 0 3 0 1 0
2 Rewind 0 9 0 0
3 Column 0 0 3 0
4 Function 1 2 1 like(2) 0
5 IfNot 1 8 1 0
6 Column 0 0 4 0
7 ResultRow 4 1 0 0
8 Next 0 3 0 1
9 Halt 0 0 0 0
10 Transaction 0 0 3 0 1
11 String8 0 2 0 1% 0
12 Goto 0 1 0 0

Now GLOB is using the index, but LIKE still doesn't because of the case issue.

NOTE! I goofed up the GLOB queries: it should be GLOB '1*', not '1%'.

https://stackoverflow.com/questions/8584499/sqlite-should-li...
Last week, on 19 October, Foxconn announced it was banning all dine-in catering at the Zhengzhou plant and required workers to eat meals in their rooms.

At the same time, the company told reporters it was maintaining "normal production" as the plant ramped up production of the latest iPhone 14 models.

I Wonder what fraction of consumers realize their apple toys are made by people forcibly confined to barracks. People who do realize this and don't see themselves as misanthropes have a responsibility to vote with their money and not intentionally buy products contaminated with human missery.
The SPA Dilemma
Before we enter 2023. We have React, Vue, Angular, Svelte, Solid.js and so on.

What will you choose for your productions and side projects?
Nitter gets overloaded and sometimes blocked. Consider as an alternative an addon [1] that utilizes multiple Nitter proxies and has a UI tool to test latency to each one. I would expect them to especially be overloaded right now with the current events going on at Twitter.

[1] - https://addons.mozilla.org/en-US/firefox/addon/libredirect/
Haiti finished making interest payments in 1947 (75 years ago). Apparently the Dominican Republic had the same GDP per capita as Haiti in 1950, so post-WW2 they roughly started off in the same boat. One of their economy's has skyrocketed (relatively) and the other has stayed completely stagnant, despite being on the same island and having access to much of the same natural resources:

https://upload.wikimedia.org/wikipedia/commons/thumb/5/59/GD...

It's always been a curious contrast and a sad one.
Not necessarily, he got quite lucky with the macro context.

The roaring 1990s stock market temporarily helped to camouflage a lot of disasters, such as Worldcom, Enron, Adelphia, and the disease spreading inside of GE. When times are that good, big shareholders ask a lot fewer questions generally.
Not that I'd say use them as the only source but they've been a source for other layoffs for a long time and he's usually correct if not always. He's the author of a few Engineering books (The Pragmatic Engineer, etc.) so he gets a lot of inside information from current and past SWEs.
Maybe a selection effect. Maybe the more optimistic people are working rather then commenting.
Or the “Computer Literacy” bookstore in the Silly Valley.
I'm not saying that arena allocators are a bad tool. It seems like a very good fit for your case, where the lifetime of a request is pretty well constrained, and issues like fragmentation and overallocation won't matter too much. But still I think the OP completely misses the discussions of these aspects.
Routing manipulation is a far more realistic threat than nuclear attack.

https://arstechnica.com/information-technology/2019/06/bgp-m...

https://arstechnica.com/information-technology/2018/11/stran...

The fantasy that life could still be lived after nuclear attack is disturbing in itself without any further "strategy".

What use would the internet be at that point? Even if you survived, your body and food is now under non-stop attack from radiation, you have far bigger problems.

Look at how miserable the world is that everyone literally gave up on protecting themselves from a pandemic.

Now imagine widespread radiation with the same mentality "well you can't see it so it can't hurt you" and further fantasy "only old people die from it, I'll be fine"
I always make performance considerations part of my specifications when they matter. Resources are not infinite! Often performances are part of the requirements even though they are implied.

Our requirement for a traffic control system might be primarily concerned with the safety of motorists and pedestrians crossing an intersection. However it's generally implied that this system should eventually allow some cars through and some pedestrians through. And that nobody is left waiting too long!

Such a system wouldn't be terribly useful if pedestrians never get a chance to cross because the light never changes.

It's not premature optimization to design your system with resource constraints in mind. It's smart engineering! A user shouldn't have input lag to scroll a document. The game engine doesn't need to render an infinite number of entities. An HTTP resource shouldn't be returning every record in the database. If you keep these constraints in mind in the design phase you generally end up with a well performing application.

Ignoring them is what I've heard called, "premature pessimization," and is a popular source of performance problems in mature applications.
Musk Polls Twitter Users on Bringing Back TikTok Precursor Vine
I understand the argument, but I find this a bit disturbing, as there are some topics that all of the oligarch-owned newspapers will not be willing to cover in depth. There is kind of a 'fringe' that will publish some details, i.e.

"(2020) Amazon: We Totally Don’t Want To Spy On You. Also Amazon: We Just Hired The Architect Of The NSA’s Mass Domestic Surveillance Program"

https://dailycaller.com/2020/09/10/amazon-surveillance-nsa-d...

However, most people view that outlet as a highly partisan right-wing opinion-centric source (with rather limited sources), not at all the 'traditional unbiased news media' - which instead avoid the story, and instead just churn out a stream of pro-government, pro-corporate propaganda 24/7. This is pretty unhealthy IMO, since, ahem, 'democracy dies in darkness', and is the kind of behavior you see from Chinese and Russian state media, not from independent journalism.
I don't understand what is the business case for acquiring an open-source framework?

Can someone explain why couldn't they just contribute or fork the project?
I think you’re really on the right track with caregiving, and would add the blind push to force people back into offices without any recognition of the costs of those policies (or, often, perceptible benefits). Going into the office is fairly expensive in any case but it especially pushes parents towards needing daycare and aftercare services which were already expensive before the pandemic and became more so after a non-trivial number of providers found other jobs, became too sick to work, died, or decided the health risk wasn’t worth it after seeing that happen to other people. Our local parents group has had stories about people choosing not to go back to professional jobs because the employers insisting on RTO weren’t paying enough to make up for that, especially if they weren’t accommodating when someone’s schedule is disrupted.
Not really but quoting the Readme:

"RustyHermit is a rewrite of HermitCore in Rust developed at RWTH-Aachen."

They wanted to keep the Hermit most probably
RAII just uses c++ constructors, destructors and lifetime rules to automatically do one thing when an object is constructed on the stack, and automatically do another thing when control leaves the scope in which the object exists. The second part (the destructor) is key, because it will be executed whether control leaves 'normally' or because an exception was thrown.
>tell me to not become a manager

Why though?
It seems inconsistent now. Sometimes I can scroll for minutes with nothing and other times I get the sign-up pop up right away. Or was it always this way?
I don't use it for my daily work but I do use it for code screenshots in talks.

I find it still looks good, with a hint of highlighting without being intrusive.

This allows the code to be the main feature of the screenshot without looking bland.
They purge people after btc/usd drops. It is a violation no matter how you look at it.
I started working around 29 years ago, pay was not great as it was a very small company and my first job out of University.

I was writing assembly code for a fire alarm interface system. Code was assembled using a DOS based system, flashed onto an EPROM for testing on the boards. Debugging consisted of tracing signals through the system, or if lucky, the boards had a spare serial port we could use to print messages.
Good. Let's make it federal next
What is great for shareholders is often not great for employees. What is great for customers is often not great for shareholders. These are often tradeoffs, so "all" is rarely an option.
I will also add that one of the big problems with TCP is that it is impossible to load balance without knowledge of the L4 protocol. You can't load balance a byte stream. That means writing your own load balancer unless you want to also accept http overhead.
I feel like the announcement that bodies of water have been found on Mars has been made every few years since the late 19th century. You'll have to drill into the details to learn what they actually found.
> don't spend the time to optimize until you have measured whether this is your bottleneck and it will actually matter

Also seen as "don't optimize the idle loop"
Same. Thus far its been pretty easy to follow along and I haven't ran into any show stopping issues.
> you carried a beeper

We had alphanumeric pagers and in the office was a terminal where one could type all sorts of stuff. Instead, the boss always typed "call shop". Nothing else. I was not willing to pay for a cellphone for myself, so if I got the page during the commute, I just continued on to the office. Where I'd be harangued for failing to find a pay phone (what‽). He always got angrier when I'd type in what he would have said if I had called in. He also got furious when I identified how one customer stole over $30k/year in inventory. That was the most dysfunctional job I ever worked at.

This was almost 30 years ago. I had gotten run over by a car and while I was healing, I started dabbling in programming around the office to organize some things that were out of control. Like the filing system was a write-only, read-never system. It would have been cheaper to just shred everything.

And to answer the OP...

Since it was all Windows stuff, I had to go to book stores and look for Wrox (red covers). Back then, they were decent, but that publisher turned into "shovelware" (a dozen photos on the cover and every chapter written by someone else, with hardly any coherence in the book). Apress ended up replacing them. And now stuff changes so fast, that books are obsolete before they can get through the publishing process.

"Source control" usually consisted of making zip archives on floppies. If the place had Source Safe, they better have good backups because SS had a problem corrupting files.

At my first "real" job programming, one clown who was responsible for a multi-million dollar product did not like to back up files. Nor use a UPS. So when his hard drive crashed, it turned out that his SourceSafe files were corrupted and we lost about a year's worth of development out of him. That got covered up.
And you have enough fuel for the generator
That was when I put aside Fortran and Pascal, and switched to Lisp, C and Perl. With some Visual Prolog also. That was the last time when I still did some UI programs. The editor was still emacs, nothing much changed.

Processes were easier, but I tried to stop people from editing as root on live machines, to have a test setup, to start using CVS (a big step forward from RCS), to start using i18n (multiple language support), and to start engaging in online communities and conferences. There was not much open source but the few known BBS boards and sources, GNU, Freeware and Shareware.

Design was waterfall, proper WBL as of now, compensation was worse, but I did work mostly as engineer and did SW programming only for the job.

Better? Better tools for sure. Tools and compilers are now free, and you have a huge free support system now.
Aliens are, by definition, hypothetical beings that are similar to us in obeying the same laws of physics. God is, by definition, a transcendental being which exists beyond the laws of physics. These two ideas are fundamentally different.

In particular, speculating about what God may want (even if you believe one exists) is entirely futile, as it could want anything at all. In contrast, there are constraints on what an alien species could possibly be like - for example, we know with essentially absolute certainty that an alien species wouldn't eat quarks, whereas there is no reason to say that God wouldn't consume quarks.

Now of course, depending on your particular religion, you may have some things that you believe God told you explicitly. In no major religion though is God just lonely.

For example, in Christianity God created us and He only wants us to follow His laws; the notion that we could evolve to become akin to God is heretical - God is only one, and He demands worship and love, not emulation. For another example, in some versions of Hinduism, God (Brahman) encompasses everything, and we are already God - we can grow to understand this thing, but the very notion of a second God is entirely nonsensical, as God is already literally everything.
> "We will exercise discretion when applying this rule. If you believe that your use-case for cryptocurrency or blockchain is not plagued by these social problems, you may ask for permission to host it on SourceHut, or appeal its removal, by contacting support."

Sounds very reasonable to me.

After all, there is a real problem which needed solving, i imagine it also eats up a lot of wasted time/cost.
Yeah, not sure if it's a mental roadblock but it's painful to incrementally improve something especially if you've learned of better ways (which happens a frequently as a jr) as you end up fighting with your own idiot self.

Bad code is laid down at day 1 and everything past that is just worsening it even if it appears to be a positive refactor. Torch the canvas and embrace the cycle.

Not that it has to be preplanned, per se, as the absence of planning before day 0 still becomes plans on the day IME.
Great point. With the baseboards off, you can even look inside the wall (e.g. with a phone camera) for clear stud bays and power cables, potentially finding easier runs.
Read TSiege's correction again, it wasn't a (bad numbers) 1000T planet being impacted by a 10T object, it was a 500T object (earth) being impacted by a 500T object (now also earth) and ejecting a 10T object (now moon) from the debris.

Without the event we'd have a planet even smaller than mars!
I think that is a good point, and one of the reasons this inflationary period seems to be so widely misunderstood and contentious. We just spent over 2 years dealing with a pandemic, there will be side effects caused by the pandemic as well as the solutions to ease its impact.

In regard to car prices, I would say that the prices themselves contribute to the inflation statistics, but they are not caused by inflationary pressure.
The network is the computer....
> the employer/employee is not a balanced relationship

Sure it is, they want my labor, I want to sell my labor. We agree on a price.

If my price changes, or they are unwilling to buy it any more I find a new person to buy my labor.

I was looking for a job when I found this one, and I will be looking again when I find my next one.
Paying to conserve the Amazon is just blackmailing yourself. Every year you're going to have to keep paying otherwise "oh no, they'll cut down the Amazon". Then once it's been going on a while, they'll start demanding more, or "we'll cut down the Amazon, and you don't want that, do you?" Unless Brazil develops some intrinsic motivation, then it is at risk. So the solution is to make the Amazon so compelling that Brazil wants to keep it.
Phonebad isn't just a city in India.
There are a few tricks to make them successful:

1. Your schema is the source of truth.

2. The protoc should generate code as part of your build (try not to check in generated proto code if at all possible).

3. Use generated code to output bytes/parse bytes (this depends on your HTTP/RPC library).

The other trick is that you should use the exact same (!) schema file for your frontend and backend projects. This means that changing it should trigger regeneration of generated code for your clients and servers and then run CI on them.

So if you accidentally introduce a breaking API change, the CI for broken client will fail before you deploy it.
Of FAANG I think only Google does that.
I think biggest problem about "premature optimisation" is the problem that defining "premature" has been left to the reader and everybody has their own definition. Then they will spar online completely needlessly because they are comparing apples to oranges.

The important thing to remember is that the earlier in development something is fixed, the cheaper it gets. The longer a problem persists throughout the process, the more expensive it will be to fix.

And "more" here means "exponentially more". Because at the time of design or discussing with the client I may be able to fix it in a second by just choosing a different option. Once it gets to production it might be either impossible or costs millions and months of development.

The job of the person who designs it is to identify which decisions will be hard to undo later if they are found to be wrong and focus on making sure these are done correctly.
It's an aquihire - they get the core team on staff. They can influence the open-source project roadmap, and get priority support for their integrations.
Blockchain over UUCP.
Its a good narrative to have as you prepare for layoffs.
How to Bypass Cloudflare in 2022
> You seem to be arguing that anything other than strictly server maintenance is wrong, immoral or unnecessary.

I suspect the OP would be perfectly fine with Wikimedia hiring translators to translate more of the 6.5 million English articles into other languages which are often considerably less developed. Or funding more development of their textbooks, dictionaries and other content. They clearly have ample funds that seem to be going to more dubious ends.
emm386 Error #06

And a subscription to the Microsoft knowledge base which came on CD (in addition to the books others have talked about)

And I vaguely remember that the debugger inserted itself between DOS and windows, when meant that it could bring crash windows if something went wrong.

Fun, but slower than today.
From my limited experience, I imagine there is a touch screen interface to do so. =p