skysight-inc/HackerNews huggingface dataset:
I'd argue that Twitter and GitHub are excellent examples of where a CDN does not work.

Some assets like logo's, headers, footers, css, fonts etc will improve greatly.

But the main content is highly long-tail. And has a very high cache-miss chance.

For 140 chars that's not going to matter. But all the images, videos, large source-codes, tarballs, builds, etc all add up. No CDN is going to help when a 30MB nightly build is only downloaded once ever. When a 2000line sourcefile is read maybe once a month. Or when a video in a tweet is seen by at most 2 followers ever.
I understand the first cycle of the process - my question is how do you repeat the cycle?
I don't think it will as it should be radically cheaper. It should come with an economic improvement.
Yes, the difference is just that one has Greek roots and the other one comes from the Latin version of the Greek word.
Not if, as R2 says, they only charge for objects that exceed a single digit request per second threshold. Your write once read once model still only costs as much as the storage at rest would.
Except Windows loves COM, and it is all about DLLs and out-of-process IPC.

Those gains have materialized in distributed computing, where the 1% cases where C++ wins in micro-benchmarks don't really matter, when network latency, databases, load balancers and the whole lot come into play.
Since we sharing :)

One "trick/lesson" I learned from working with a "big dist system" (think scraping-jobs) with lots of clients(read unique errors) and requirements was:

Never-ever-ever do:

if(client->id=123){

//do special workaround,process,feature or magic-dance

}else{

//normal non-magic-dance,process,flow

}

The only "allowed method" for implementing such code was to add a "JobOption" to the client-config.

Thus you have:

if (client->joboptions->magic_dance){

//magic-dance-feature-workaround

}

You'd be surprised that over time how many clients have "similar requirements" but different combinations and just being able to do a checkbox-check on their job-config (enable magic-dance) was gold for maintenance and keeping out the spaghetti code!

It was the 'greatest of sin's in our org to write "if client->id=123"
Also for a historical fiction take, Ken Follett’s “Pillars of the Earth”

https://en.m.wikipedia.org/wiki/The_Pillars_of_the_Earth
> Violent mobs also have democratic legitimacy,

No they don’t.

> And on the contrary, it is by making the situation unbearable for everyone that popular and political will to change a broken system is created.

When has that ever worked?
You could start by encoding the deltas using variable length encoding, so a 0 delta could be as little as 1 bit. But anything off-the-shelf should be able to compress this type of data well.
You should be more careful advertising your age.

Under 13s usually end up with their accounts forcibly deleted because of laws about collecting data [making it disproportionately inconvenient to facilitate young children].
In short: don't let your users become your product managers. The real PM's exist for a reason.
https://www.youtube.com/watch?v=aZ9MFts28XI&lc=UgzhE63LoInoN...

4 hour video of Epik CEO on livestream.
Can I run this in an LXC container? I’ve been having a hard time getting Wireguard to work under proxmox…
Many people feel compelled to write in this way. They think that if they don't make it personal, the reader will get bored. It has to include some story you could relate to. A good example is Avi Loeb's Extraterrestrial: The First Sign of Intelligent Life Beyond Earth - for the first half of the book you can only wonder when the author stops talking about himself.

Sometimes, although rarely, this makes perfect sense, as in Surely You're Joking, Mr. Feynman! - but in practice everybody thinks they're special.
For all we know, Pi is random (i.e. normal, although we haven't been able to prove it). That would mean any sequence appears eventually, with uniform odds. Hence any ("interesting") data you'd want to store does appear at some point, and I gave the odds of any (interesting or not) digit string appearing in the first x digits.
See also [0, 1] from previously [2].

0. https://orgmode.org/list/CA+G3_POBAB1QX1Zv8q9sjFh4KHUHVmaNXp...
1. https://github.com/tgbugs/laundry/tree/next
2. https://news.ycombinator.com/item?id=28095196
I didn't realize it, but my '72 Dodge has a switching power supply to convert the 12 volt system voltage to 5V for the dashboard instruments.

It's a very simple device, relying on current heating a wire to bend it to and from a contact, but it's an engineering marvel of low cost effectiveness.

But it doesn't produce "clean" 5V, there's a jitter to it. Some electronics guys have replaced it with modern circuitry (an op-amp I think) but it turned out there was a problem with clean 5V. The jitter would unstick the the analog dials, so they'd display accurately. The clean 5V didn't do that. So, they had to add more circuitry to add jitter in the supply voltage.
A very interesting approach I have discovered recently is "Zettelkasten".

To summarize:

- Whenever you're reading/learning/researching/thinking something, you write down "fleeting" notes in your journal, just jotting down ideas you don't want to forget. It's effortless and natural, doesn't feel as scary as writing, you're not staring at the blank page, you're just collecting useful ideas as you live and work.

- Then you try to process these notes regularly (daily or weekly) - take the key insights you want to remember, add them to your "writing inbox", through the inbox and turn the notes into "evergreen atomic notes" - a cleaned up and organized version of your fleeting notes. You turn each useful idea into a single, concise note with a good title. One concept per note. Interlink the notes - link the note to related ideas, add tags, put notes into folders, whatever makes it easy to search through them later on.

- When it's time to write, you have an archive of all the most useful ideas you have learned, organized by subject, interlinked with each other. Now all you have to do is take several related notes, compose them into an article, edit and fill in the blanks.

So you never have to stare at the blank page. You naturally write as you live, then you organize your thoughts a little better into the evergreen notes, then you organize these notes into articles, videos, books, whatever you want to produce.

You can learn more about it in the amazing series of posts here: https://publish.obsidian.md/andymatuschak/Evergreen+notes

I got into the whole thing after learning about Obsidian (https://obsidian.md/), a cool app for writing and organizing such notes (no affiliation, I just like it).

I was already writing down all my notes in Editorial (a really cool iOS app, unfortunately hasn't been updated in a long time, 1Writer is a great alternative). But I would never reread them or turn them into anything useful to anyone. Taking the extra step of cleaning up and organizing my notes is very helpful, now I do this for everything - personal stuff, my work projects, everything Im learning about tech, writing, etc.
Nice, I was just reviewing SVD and PCA, I grok them but then I forget, this material is useful for remembering the big picture.
This is just begging for a malware command&control system for SCADA controllers based on embedding commands and responses in the raw float values of some sensor data streams..
Rust for the Polyglot Programmer
You’ve got it backwards. It’s precisely because science is ever-changing that censorship of specific views is harmful. See, for example, the Soviet Union’s bet on Lysenkoism.
Certainly we'll have all of the above.

> Will it be spun as the green energy sector not making their minds up and flip flopping between solar/wind/fusion/etc?

Well, the green energy sector is big. Solar companies push solar, wind folks push wind, and well, fusion folks are pushing for funding and VC money.

But the important thing is, we need all of them. Plus batteries (and battery-like systems).

And, yes, there will be spin doctors trying to discredit "green" because X, but that's what they do anyway, fusion or not.

> Will there be stories about how we could accidentally create a black hole and destroy the world?

Good idea, maybe :D But we'll sure hear a lot about how much irradiated/activated waste it will produce, and how it's not green at all, and so on.
Nintendo categorically denies that a 4K Switch Pro is in development
>I have a singular request - so Wireguard is unusable in any high security environments with compliance requirements - because it doesnt support any 2-factor auth out of the box.

>We get rejected on stuff like PCI-DSS because the standards mandate a 2-FA. I am not a security expert and wouldnt know about the pros and cons here. But the fact remains that most high-sec compliance needs 2-FA.

This is absolutely nuts. Why would 2FA be enforced at the network edge instead of on individual services?

What a completely suicidal security model.
This just shows how ass-backwards the whole industry is with its "standard practices", a lot of which I see repeated as advice in the thread. It goes like this:

1. Push a product (or these days, service) at people. Preferably a captive audience. In B2B, that may involve growing an "internal champion" at a customer company, preferably a manager that doesn't need the software themselves, that can be bamboozled by your sales people.

2. Don't explain how the product works or what it does to your sales people. That's techie stuff. Also, once you give your sales people the license to bullshit, it literally doesn't matter what the product does[0].

3. Don't ask your users what they want or like. They don't know what they need. Rely on thorough surveillance instead, as a good "data-driven" shop you are.

4. If some users manage to somehow deliver feedback to you, ignore it. Users don't know what they want, and can't articulate solutions.

5. If the client does not understand how the software should be used, that again means they just don't know what they want. Interfaces are designed to be intuitive. No training is ever necessary. Software manuals? That's so 1990.

6. The so-called "power users" are making point 5 harder. Ignore them with extreme prejudice. After all, them being more productive doesn't earn us more money.

It's a self-reinforcing pattern of industry-wide self-delusion. No wonder so many non-tech people hate technology.

On the "XY problem" someone mentioned in this thread: one of the biggest problems on StackOverflow and other forums, and previously on IRC, is that quite often, the person asking for X actually wants to know X, not the Y, and they especially don't want to have their sanity or competence questioned.

--

[0] - Per HG Frankfurt, bullshit is when you don't care if what you say is true or false, as the reality is orthogonal to the goal you want to accomplish.
> (115 bits -> 14 UTF8 characters)

Not exactly. If the 115bits are the hash/retrieval key of the actual content, then that can be a lot of information. Just have to have a big enough DB.
We considered it, but (in this case) the application's use-case is on shared/communual "front-line" machines (hence why we added quick-user-switching), so even though ostensibly a single, human user is logged-in, we honestly don't know who is actually using the machine, and some other user who is just borrowing a machine could easily dismiss a tour/onboarding intended for the actual user who is logged-in.

If you think that's bad, when we overhauled some incompetently written code (from a dodgy contractor before I joined) that stored passwords using reversible-encryption (ARGH!) - which was for a "feature" that allowed tenant-admins to reveal their own users' passwords (WTFBBQ!) - and switched to using correctly hashed+salted passwords we had dozens of support calls from angry/frustrated (and yet unsophisticated...) users who said they were no-longer able to login because they never bothered to remember their password, they'd just ask their tenant-admin to tell them their own password (aiaaiaiiaiaiia) and now they couldn't do it anymore. We asked why they couldn't use the forgot-password page or a magic-link to login and they said it doesn't work because they all used fake e-mail addresses for their users (*dies*) (these tenant accounts were all set-up before things were fixed, and accounts with invalid/unverified e-mail addresses were just grandfathered-in).

We do also support OIDC (we are our own IdP, as well), so to try to make things easier for our users we'll be adding O365/AzAD soon, with sign-in-with-Google (and maybe sign-in with Facebook... excuse me while I take a cold shower) so at least some users can dispense with having a separate user-account they need to remember details for.

...so things were awful, now they're just bad, and they're getting better - but things could always be worse: Our main competitor is an on-prem VB6 app that pushes data to a "cloud" (i.e. Internet-exposed) SQL Server running off a business/residential IP address with a hardcoded SQL login userID and password shared by everyone (all of their tenants!).

------------------

...this is what the LoB software world is like. There is so much room for improvement everywhere - but all the competent uni grads join some glamorous FAANGMA company after school (well, I'm guilty of that myself...) - but I wish they'd consider un-sexy LoB software: it pays much better than FAANGMA provided you're competent and know how to negotiate. I think the LoB area gets a bad rep just because it's generally where (for want of a better phrase) less-talented people end-up which brings down the average total-comp.

I'm rambling at 3am again, ugh...
I want to know how a person can just do something that's bad/fraud and not feel bad. I'm a yes man/nice guy to my own detriment. Is something off, they just suppress the idea of morals, idk.
Here is a Java/C++ audio workstation software,

https://www.bitwig.com

And here is a must read book to do great UIs in Swing,

http://filthyrichclients.org

Here are examples of Java applications based on Microsoft's Fluent UI design,

https://www.pixelduke.com/java-javafx-theme-jmetro/
New Source for People Data and Profiles: Kelvindata.com
"You hear, 'Hey, boy, come here, N-----.' or 'Go back to Africa,'"

“Swasticas and kkk symbols in the bathrooms”

Come on. Are we really to believe this is happening at Tesla…
Absolutely.

Putting on my hypotheticals hat, part of it will be:

- not being in the room where it happened, and presuming that the only impetus for change is evil, which feeds into our own deep-seated resistance to change.

- not knowing which voices are being paid to speak (news media, social media, etc) and which voices are completely under-informed - compared with knowing which voices are definitely being paid to speak (government mouthpieces, propaganda) and conflating "don't know whether to trust" with the much simpler "don't trust".

- knowing that sometimes Governments do good things for good reasons, but even then they often end up producing terrible unintended side-effects, or end up being polluted by less-than-wholesome agendas as a price of getting enacted.

So yeah, I totally get that it's hard work overcoming all that to get to a point where you trust anything the government does.

The real irony is that it's often government inaction that we should be more suspicious of - it's the status quo and anaemic half-arsed reforms that more often feed into the pockets of the powerful while giving a veneer of progress.
The best way of creating a landing page is making research and look throught 100-1000 great landing examples that are already work and look pretty good.

Just spend few day here at this curated and inspiration platforms:

1. SinteInspire

2. Land-Book

3. Lapa Ninja

4. GodlyWebsites

5. SaaSlandingPage

After that you will understand what type/structure/design/features/texts you need for your own product.

Good luck!
Yes, but no.
If your protocol or your implementations have holes, you may loose messages because of that, and in a lot of applications, it's unacceptable to have the transport protocol dropping packets.
That must be why WinUI is written in C++, Metal uses C++ shaders, or CUDA hardware is designed according to C++ semantics, then.
"But, unlike more than 200 human solvers, it wasn’t perfect on all of the puzzles: It got waylaid on two of them and finished with errors."

I'm curious, what kind of error are we talking about? Words that don't exist, or another solution to a problem that may not have a unique solution?
So, are you saying this is just a natural inclination in some authors?

If so, it makes you wonder if most people actually _do_ want to see such a personal touch in what they read -- no matter what the topic is.

Perhaps it's just me then who can't stand it, at least not when it's completely orthogonal to the topic at hand.
The question being of course: what happens when you lerp of two such "single parameters".
While using a runtime written in C++.....
I don’t understand the appeal of this type of fusion (as opposed to the plasma reactor approach). We’ve known how to get positive energy out of fusion fuel since thermonuclear weapons in 1952. The really hard part would seem to be capturing that energy efficiently. This experiment is stuck at the ignition phase. When that’s positive energy they won’t be done, they’ll be able to start working on the practical problems of sustaining it. What am I missing.
>Asking users what features they want is pretty much not fair - because most people don't have the skills to think through and answer that question, nor is it their job to do it.

100%, Usually early in the "project discussion" I try to boil it down to just ONE CORE PROBLEM they have.

For example:
If you had a magic wand that could generate ANY SOFTWARE to SOLVE ANY problem in your business (but restricted to ONE problem). What would that problem/solution be ?

From there it's usually easier to generate a feature-list(requirements) as long as you solve the damn core problem :P
innovative!
well done.
I'm ADHD and Org-mode has majorly improved my capacity to organise my life, because it has let me create a system that integrates most things I do in a way that works for me and my quirks.

My current setup is....

- Capture todos as they pop into my head, inbox, browser, rss feed, etc, into a simple daily.org file whose parents are the dates of the events. Here's the org-capture-template:

("c" "Do on date" entry (file+olp+datetree "~/org/daily.org")
"\* TODO %? %^G\n%t\n%a\n" :time-prompt t :clock-resume t)`

It outputs a tree like this:

** 2021-10 October
*** 2021-10-01 Friday
**** TODO Reply to Cecile about buying keyboard :PERSONAL:
<2021-10-01 Fri>
[[mu4e:link-to-email][Re: Hello]]
*** 2021-10-04 Monday
**** TODO Haircut :PERSONAL:
<2021-10-04 Mon 11:00>

- If it's part of a big project or more of a datastore, give it its own org file, and refile captures there. Use org-taskjuggler for Gantt charts.

- If it's a long standing task (eg work on book, read Practical Common Lisp) set it up as a habit so that not only it repeats at the desired intervals but I get a diagram which says how well I've kept it up.

- Anything to do with friends and birthdays go in contacts.org, so that I can keep an eye on how much I see people.

- Load up Org Agenda and commit to a todo by clocking in (I). I almost never check how long I've spent, it's more just about committing to myself. Mark things as done (t d) as appropriate.

- Archive DONEs ($) intermittently rather than immediately, so that I can remind myself that I've done stuff.

Stick to the rule that TODOs are only for things I expect myself to actually do, rather things I want myself to want to do. (my cycle is TODO DOING WAITING HOLD | DONE CANCELLED SCRATCH).

I used to have different org files for different projects/aspects of my life but refiling things created too much friction. Most things just need to go into daily.org, and that's fine.
Functions (procs) and other state are not shared between interpreters. So they do need to be reinitialised in each thread. This is not hard to do though. The messages which can be passed between threads can be arbitrary scripts to be executed in the target interpreter, such as proc definitions.
Absolutely!

I often wonder whether the epistemology we are "born with" can actually be improved very much (in a general sense), or whether the best we can do is teach domain-specific techniques to override our defaults on those topics.
I really never understood writer's block.

I can write 10000 words on the spot on any random word picked out of the dictionary. Even a one I don't know at all.

Friends loved to test me on this, picking up some BS topic and see if I can come up with a scenario or a song. Then after a few minutes of my rambling they get bored of course. Having something to say doesn't mean it's interesting.

My problem is rather to learn to shut up about things and accept it's usually wiser to not have an opinion on most things.

The vast majority of words do not need to be spoken or written, but it's hard to do for me.

Case in point: was this comment worth writing?
Is this one of the most brutal hacks in recent history?

Can’t say it’s not deserved considering the scope of data exposed.
No it's a failure to get the right people involved at the right time. I'm currently a CTO and I also do product management currently. So, whenever this stuff goes wrong it's actually both my problem and my fault.

My solution is to listen to sales and get involved in early in the sales pipeline to figure out what it is that our customers need and manage our roadmap accordingly. After the deal is closed is too late to do anything. Two things I've noticed with this is that sales people are selling what you don't have and not selling what you do have. Whenever that happens either you have the wrong product or you need to get your sales people up to speed with what the product actually is about. The worst is having features that would solve a problem that sales is simply not aware off or misunderstanding and therefore not selling to the companies they talk to.

The key thing is involving the right people throughout the sales and requirements process and closing deals that align with roadmap & product and ensuring that near future product work aligns with what our sales people need to be able to close deals.

When talking to customers, it's important to realize that the person purchasing is not going to be the person using the software typically. So there's a big risk of a he said that she said that he thinks that's what our users need summarized by the sales person as "the customer needs X, when can you deliver that". Most SAAS products sell a promise to IT managers that don't actually use the stuff directly but instead manage people that manage people that actually have to use the software. With sales in between development and all that, that's four levels of indirection.

Breaking, through that and getting to the core of the issues is important. Having people in the room that understand both the business and technical constraints as well as the actual domain and users is key.
Okay, I think you are right. The power-off thing is new for the newer iPhones with iOS 15, for the older models with older iOS it's available only as "No network but power on".
I Found a Great Sidplayer
How deep learning is transforming design: CV and NLP applications
He-Man joins fight to save Malay shadow puppets
If you use iOS, Musi [0] can replace the YouTube app for viewing with no ads, recommendations, etc.

[0] https://apps.apple.com/us/app/musi-simple-music-streaming/id...
You’d need security for this to be a brutal hack.
I'd assume that at this point anyone signing up is (or should be) aware that the military can arbitrarily extend their service time?
Never heard of Snowden, eh? :-D
> There's no error handling at all right now - if any file operation fails then there's no information given, it just goes splat.

> There's no tests - and I'm not writing any - I made this project for me and I don't need tests.

Not exactly production ready!