skysight-inc/HackerNews huggingface dataset:
Lying to customers isn't good, but lying to investors is a crime against rich people & will certainly cause trouble for you.
And let’s talk about deaths due to cold weather?

I’m all for conserving the climate. The doom and gloom has been media’s staple for over 50 years. Now, it’s taking on the vibes of “We’ll all die if you don’t adopt authoritarianism. We want to monitor your carbon footprint.”
Isn't this "cat" as a static site generator target than "make"? Make is just the build system invoking the static site generator.
The irony is that he literally helped bomb Iraq (he was Clinton's vice president) for the same oil he's critical about now...
What solutions he suggests besides green capitalism ?
Hypocrisy is an art
> I cannot prove it, but I think some of these UI and UX horrors are caused by the ever present need for software to change in order to demonstrate it is alive.

The sad thing is this is largely driven by managers trying to keep their teams looking busy, and not by customer request. Most of the time, users will ask to make something work better or actually work. Make-work requests often site some internal usability/HIG guidelines without having any user interest at all.
I think in Asia though it's expected of highschool students to evaluate the integral without a calculator. Education in the US should at least match what they do in Asia to stay competitive.
A very good question.

For a green thread implementation as featureful as a platform thread, there is no fundamental reason they can not be made almost equivalent (there are a few minor hardware overhead limitations performance wise, but they are fairly negligible). But, in practice, platform threads on most kernels have large amounts of overhead that increase their cost beyond what would be theoretically necessary, so the benefits of green threads are overstated.

However, one major advantage of green threads is that they do not need to be as featureful as platform threads. You can remove features so it fits your exact needs on a per program basis instead of having a one size does all implementation.

For instance, you could use a smaller stack size. On most operating systems, they require stacks to be a multiple of the memory mapping size to allow more robust stack guards. You can get away with tiny stacks on a green thread if it works for the program.

If you know for certain that you will not use certain registers on a green thread you can reduce the size of the task control block to omit the registers.

You can choose a simpler scheduler amongst the green threads. This turns out to be the source of very significant improvements. Task scheduling code is actually the vast majority of context switch time, not hardware costs like most people believe.
Haha I sense a trend for these home grown static site generators :-)

Yours are much more advanced, but a few years back I made a minimal PHP static page generator and named it...

PHP keep It Stupid Simple, or in short P.I.S.S.

https://blog.nyman.re/2020/10/11/introducing-piss-a.html
You could in principle stipulate that the aid is only offered as long as no new coal power is being constructed (so maybe just a few strings attached). That would get rid of the option to siphon [too much of] the money for military purposes.

Regardless, my point was that there are many options besides war for quite directly reducing other cointries' emissions. There may be second order effects, so I'm not necessarily advocating for it, but there is certainly no reason to say "we've done all we can".
I think there's a big difference between transducers work and how other lazy stream libraries work. Not too familiar with LINQ but more with Java streams and Scala views and iterators. Usually these libraries wherever the work is forced, like in a final call of `.toList()` or whatnot, they are materializing something like a stack of iterators. Each iterator calls its child/children iterators and the pipeline logic is in the stack of `.next()` calls.

The difference with transducers is that the transformation logic is completely decoupled from the fact that this is happening in collections. That is what makes them usable outside of the context of collections, most famously in core.async where you can map/filter/mapcat/flatten/take/drop channels just like you do with collections. This only works because transducers are completely decoupled from either the fact that elements are coming from, or going into, a collection. I think it is a really fascinating and creative achievement in decoupling. Java Streams and Scala view/iterator/iterable transformations can never be reused in other contexts since they are fundamentally about the collections. Whatever kind of Observable/Async Stream/Future or other places where you might want map/filter/reduce functionality has to reimplement the whole set of these operations anew (see for example Akka Streams, RxJava)
Have you tried rejoining the scene? These days I see my local game store having wargame nights, Magic nights, tabletop nights, etc. I think the market for all of those has exploded over the last decade and there's sooooo much gaming of all sorts now. Truly a nerd's paradise :D
I thought hacker news was anti-clickbait?
Nice! I will keep you updated on my progress :)
Sometimes sequence programming logic is easier to write and understand. Network streams being an example for me. The benefit I see of transducers is that it allows you to think with that model. For example if I want to find all image files on my computer, remove duplicates, etc. The processing is much easier for me to think about if I can think of it as one file at a time. Then some more sequential programming based on other characteristics of the file - like batching where and when it was taken.

I like the concept so much that I built a JavaScript version using generators.

Unfortunately, I do am not a fan of JavaScript at all and it appears that clojure now requires that I install a JVM. I realize that this is a very personal issue, but I am a "just say no to Java" person after using it for 10 years.
Although it doesn't directly go against what you're saying, many Unix daemons have supported HUP signals for decades which can achieve the same outcome. No need to configure via API, just change the configuration on disk and send HUP.

I suppose arguably that becomes a bit trickier for containers, so perhaps that's why you'd want to configure via an API?
"there is actual science"

There is SOME truth. but not all of it.

Just like there is truth in religions - be nice to your neighbors. Do unto others. Truth. surrounded by bullshit (religion, dogma, etc).

There is truth and "actual science"... but there's also half truths, lies, bad prophecies, etc.

"you can cherry pick" likewise, you can cherry pick some facts about carbon... and then ignore stuff like the destruction required to make batteries, the inability to recycle a MASSIVE fuckton of "green" (wind mill blades, batteries, solar panels, etc - all ending up in land fills).

"models" yeah... except that models are limited, have increasing error rates and you end up with the spaghetti modeling with the simple stuff like weather for next week - much less the weather for next year.

Speaking of cherry picking... you'll cherry pick one or two models from a decade ago and ignore the 100+ others that are wrong.

"political not science" it's both. and religious. It's faith in models that have been cherry picked while ignoring inconvenient truths about "green" solutions that are based on bad models that can't be proven and that don't cover all the possibilities.

the problem with your response is your apparent faith in science and, like a Catholic who will downplay problems with priests, you'll ignore the parts you are uncomfortable with.

climate change is real (little c, little c). Has been happening for... all of history.

Climate Change is not (big C, big C). It is a religion.

One is based on facts and science. the other is based on faith.
its a beta version, there're no guarantees or anything like that

"Contract, test and evaluation period

The test period of the product begins on 01.06.2023 and applies to the non-guaranteed maximum duration of one year. We reserve the right to refuse service to any person at any time for any reason.All files will be deleted after expiration of the testperiod. The service can have software bugs which can result in losing data."

https://info.scramble.cloud/index.php/terms-of-service/
Large Herbivores Can Help Prevent Wildfires
Their business model seems to be "simply" for users to pay for storage.

From the ToS: "The test period of the product begins on 01.06.2023 and applies to the non-guaranteed maximum duration of one year. [...] Prices for our storage solution are subject to change without notice. We reserve the right to change or discontinue the Service (or any part or content thereof) without notice at any time. [...] We may, at our sole discretion, limit or cancel purchase quantities per person, per household or per order. "

Also, "We reserve the right to restrict or prohibit any extension of the store which, in our sole discretion, appears to have been placed for illegal purposes."

And an interesting caveat: "We explicitly point out that we do not guarantee that there will be no data loss or that our product will be available at all times."
thanks! CicadaLang looks very interesting
I can assure you that Deloitte has absolutely zero exclusivity to that description.
The guy is living in the suburbs, which means they aren’t going to the store very often as they probably live far away from it. That means they are getting more than a few bags of groceries, they don’t need an F150 for sure, but they probably aren’t getting to carry this with an e-bike.

Better for the suburban guy to become a city guy and walk or bike to the grocery store a few times a week. They get better veggies that way as well.
It's definitely interesting how people with the same title can have such different experiences. I'll try to give the other perspective, but please understand that it's a huge topic and this is a simplification.

My experience has been an issue is raised - usually by management or "the business", but sometimes by engineering. "Our website is too slow!". Now someone has to step up and clarify things. Like:
* what does "fast" even mean for our website? It would be great to have an objective metric.
* Is there such a thing as "fast enough"?
* How much time / effort / money is a given improvement worth?
* How do we prioritize this vs. everything else we could be working on?

A project spec comes out of those discussions, but the discussions themselves have significant technical and business inputs.

I don't view taking part in these discussions as "extra" responsibility, I view it as a core part of the job. I've also seen what happens when specs are written without technical input: it makes implementing them a lot less pleasant.
Maybe the new cities could be built to be walkable.
Might I also add:
https://youtu.be/aVwxzDHniEw?feature=shared
Which works through them from first principles with beautiful animations.
Totally, that's why I don't trust anything anyone says, ever. I can't trust that my fallible brain is hearing what people are saying correctly, so even if they're right my understanding of what they're saying may still be wrong.
As someone who works as a service designer and design strategist, I agree, 100%. I’ve seen a general decline in rigor in the field. Many are back to making things “pretty” with poorly done research (if that) asking small-minded questions rather than thinking about context, ecosystem and systemic effects of their design decisions.
I'm not sure I agree that just saying "I dropped out of Harvard" is a bad thing. After all, Harvard is putting their name on the "Extension School." If they didn't want to trade on their reputation, they could have called it something else.
OpenBSD: P2k23 Hackathon jeremy on Ruby cleanup, database progress, et
https://www.nature.com/articles/s41467-022-31558-z
Yes, logs are important for running the service. You were supposed to realize when you said that, that “is this useful” is a factor in how long you keep logs, alongside “how much does it cost”.

I do work at big tech and see a lot of logging policies, in fact. Having lawyers involved doesn’t make it “no legal considerations”, it makes it properly assessed legal considerations. It is default practice across big tech (and other large professional industries) to delete eg email as soon as reasonable in order to reduce discoverable records. It is also required for most services that they be able to delete logs and archived material to comply with the laws about keeping personal data around for no purpose - most places will never see this brought up but if they do, it can be a big deal.
Are cold weather deaths increasing or predicted to increase significantly? If so, then that does sound interesting and should be discussed.
I think the issue is not one of expertise, but that many people are arguing without being aware of facts contrary to their own view. For instance a critical component to the conspiratorial view is Operation Northwoods [1]. And it tends to paint a far different than picture than you are claiming. Operation Northwoods was a planned CIA operation where they were going to carry out terrorist attacks against both civilian and military US targets (notably they even proposed the use of remote controlled civilian aircraft) and blame it on Cuba, so we could start a war with them. This plan successfully made its way all the way up the chain of the command and was one signature away from being executed. The problem is that JFK rejected it, vigorously.

The CIA and the military wanted global escalation and military conflict. Kennedy, by contrast, was working more towards reconciliation and global peace through good faith. Just prior to Operation Northwoods, he had recently removed the head of the CIA (following the Bay of Pigs catastrophe), and following the Joint Chief of Staffs presentation of Operation Northwoods to him, JFK also removed him from power as well. JFK would then go to on to pass a unilateral nuclear test ban as a show of good faith to the USSR, and was reportedly not only looking to withdraw from Vietnam, but also to completely dismantle the CIA. Less than 6 months later, he would be assassinated.

That's hardly a tale of some 'shadowy elite trying to control the world.' In fact the assassination becomes so utterly predictable in this context that one has to consider that if it was a simple lone-wolf then the CIA and military effectively won some sort of one in a quadrillion type lottery (at least from their rather sociopathic worldviews). For that assassin to then to be assassinated, after initially claiming he was a "patsy", and all the other weirdness around it all, I think Occam's Razor starts pointing in a pretty clear direction.

[1] - https://en.wikipedia.org/wiki/Operation_Northwoods
Even better: https://addons.mozilla.org/en-US/firefox/addon/sidebery/
I guess the most annoying weed in my yard is oak tree saplings then! Not only unwanted but hard to remove if it gets established.

The acorn woodpeckers and/or squirrels keep planting them in places I cannot afford to have a tree. Its roots would eventually cause a lot of damage.
Flask extension for server-side sessions
> Big vehicles should be for men on a jobsite, not pretty trophy wives.

Exactly, they belong in a job site, not tiny cramped urban areas. You see most SUV ads invoking mountains and nature and off-road driving. You don't see them bragging about their Walmart grocery carrying capacity. If SUV drivers can't drive properly, they should stick to the suburbs where roads are wider.

> This reminds me of a conversation on here the other day, as soon as people find a group they feel it's socially acceptable to hate on, they're all over it.

That's called being human. Bad drivers are not a protected class anywhere.
This type of convertible note you're describing is almost never used these days.

As I VC I talked 1000s of companies fundraising and it was not something founders ever sought out

SAFEs are almost always the alternative to priced rounds
It's more about trying to work out what motivates people to do things while using some reasonably simple tools like the N/N web heuristics to guide you. More a way of thinking straight about what qualifies as a good design under a certain condition, and what hypotheses to research and test out of that. So it's contextual. It may seem like there should be a more logical formula, but there's really not a lot of technical/formal things (along the lines of, say, accounting or structural engineering) that lead you to the best approach. My frustration is not that people don't necessarily know about these things (although I bet if I mentioned Bruce Tog to anyone at work they'd give me a blank stare), but that they can't marshal them in their work.
Well, if you see my templating code, I've basically written PHP, but in Bash :D
It's block size is something stupid like 16 bytes, so it effectively becomes a slower linked list.
Historically I think there's a very strong case that Symbolics did outperform others with their software productivity, especially in graphics. They had an ability to wade into certain domains and produce legitimately shockingly competitive products, which really should not have been possible.

But I also think Lisp leads to spectacular burnout as I think it imposes a greater cognitive requirement on the part of the developer.

A Symbolics graphics reel from 1989 https://www.youtube.com/watch?v=V4HXPJtym2Q

This stuff was still in use on Final Fantasy 7 https://lunduke.substack.com/p/the-computers-used-to-do-3d-a...
Love this article.

1. Developing beliefs and acting on them is a key part of leadership.
2. Without it, you limit career advancement.
3. It's a skill that can be learned.
There is a lot of rote in Asia, and an over emphasis on classic geometric proofs that have little relevance in today’s world. Yes, we should try as hard as Asia in math, but blindly copying Indian or Chinese education practices isn’t the right way forward.
You can (kind of) emulate linear types by making `drop()` unlinkable[0]. Of course, I wouldn't recommend doing this since the error messages are awful and give no explanation at all of where the actual problem is...

[0]: https://play.rust-lang.org/?version=stable&mode=debug&editio...
My dad kept a diary during his WW2 duty. In his 80's, he read it and was shocked to discover it did not line up with his memories.
Lol thank you for the clarification! And here I thought, "Man, that's not how I remember those cards. I didn't realize 90s printed cards were so pixelated, with Arial and bad border control everywhere. I must really be getting old."

Makes me feel better that it was just a video game :)
Eh, Apple's ideas are not to be taken as gospel. This is the company that fielded UI that's as bad (or worse) than everything we're complaining about here, decades earlier.

For example: secret alternate menus. You can actually press modifier keys on the Mac while a menu's open and sometimes you get totally different menus. These are not indicated anywhere. So theoretically every menu on a Mac may have... let me do the math here... eight sets of contents using Control, Option, Shift and all combos of those. So according to Apple, you should open every menu and mash every combo of modifier key to see what's in each... and memorize them.

Another Apple menu defect is to start every entry with the same word:

VIEW

Show meters

Show clips

Show this

Hide that

Hide the sense

Show WTF the point is

This makes the first word of every entry nearly useless, and massively degrades the usability of the View menu. You have to sit there and parse the first part of every line, which only has two options... both of which are four characters, BTW, and thus visually the same size.

You don't do this; you use CHECKMARKS, which we learned decades ago. Some Mac apps do this, but many Apple ones still have this asinine convention of "show" and "hide" repeated over and over.

VIEW

• Meters

• Clips

This

• That

• The sense

WTF the point is

But that brings us to another classic Mac menu defect: The misuse of the Window menu. This menu is supposed to show names of open windows in an MDI-type situation. But Mac apps often bury View options in the Window menu, apparently expecting the user to guess that whatever they're looking for has been implemented as a window. Why would I go into the Window menu to activate audio meters, for example?

And most of the time, whatever the option is has NOT been implemented as a window.
Here's the source code:

https://github.com/dhruvmisra/changelog-focus

Would love to hear your thoughts and get feedback.
I don't have experience with Clojure, but this description makes transducers sound like simple pipeline of functions transforming a stream along the way. This is quite common and readily available in any language, it's also how Unix piping works (for text/binary, but that's a stream of chars/bytes), and I'm wondering why was the name "transducer" required.
What didn't make sense to me about that story is that even if their payroll system wasn't submitting the tax payments to the IRS, it seemed it was witholding the tax on the payroll. So the money was sitting in an account somewhere, they should have had it available to pay all the back taxes. They would only really be out the penalties, which could probably have been negotiated down on the basis of an "honest mistake." Though he did admit to sloppy bookkeeping overall, so maybe they saw all this money in the bank account and spent it on other stuff.
Ask HN: Private Company Stock Options
I know little about stock options, and usually people talk a lot about them in the context of publicly-traded companies and being employee number X (where X < 100). In my case, the company I will work for is a private one, and I'm probably employee number 1000, so stock options are really not that of an incentive even though the company advertises them as "perks". I'm really more into negotating a decent base salary.
> Hypothetical: They checked with an agent who is deep / high up in some foreign agency and he said "wasnt us." that agent retired but helped recruit others. those may have retired and helped recruit others.

> Just that one connection in a file, "we asked agent $name and he said $agency knew nothing" might be justifiable to keep secret if theres a connection to someone still active.

The names of the agents would be redacted at first place on declassified material.
Can't be natural selection, can it? Sheer luck?