skysight-inc/HackerNews huggingface dataset:
Stacks are reference types, the operation doesn't produce any new values. Half the time you want it there to push more items, or to display it in the REPL like in this case, but the other half you're going to drop it anyway.

I'm still undecided on the stack ops. There is one case in forthy2 where a reference is left on the stack, and that is splicing values into forms [0], where it's more likely you want to keep working with the same form. More likely is not a very good heuristic for designing API's though, so I might just go with the behavior you expected.

[0] https://github.com/codr7/forthy2#quoting
This is so true. Audio APis are poorly documented. I have only done my task by customizing examples :).
Sure, and actual real people (even smart, nice, capable, well-meaning ones) sometimes turn out garbage, or don't even try to produce.

Ignoring that out of kindness is silly. Any good professional should welcome honest feedback; if you can't criticize a $T company because it might hurt someone's feelings...

Complaining about the docs is important feedback, aimed at ultimately making Apple healthier. And getting to the point where the docs are sub-par means priorities have shifted over a period of years, and will take that long to get back in shape. That's not on any one person, not even Cook, except in the ultimate responsibility sense.
Hash passwords Use Docker to compile Bcrypt and don't link host node_modules
My issue with this is that the developer is comparing his experience with Apple's documentation over a few months, with his anecdotal experience over 4 years.

Part of gaining experience with a platform is the ability to source answers to technical questions effectively, including how to use official documentation effectively.
Atmospheric Scientist on the CA Fires
I actually agree whole heartedly with the intentions behind this article. I find Apples documentation to be incomplete and not nearly as detailed as I think it should be.

I think that personally it’s not all that well organized either.

My minimum standard for good documentation has and always been Python’s[0]. While no documentation is perfect, I think they mostly get it right by providing good explanations and examples consistently throughout the documentation. I also like how it’s spilt up between modules and the code examples are routinely updated. I have found very little issue with Python’s docs. While it could definitely use more examples and and deeper content around asyncio in some parts (mostly around transports and protocols) on the whole its very good, to me it’s what all organizations should strive for at a minimum. I also want to call put Mozilla’s Developer Network (MDN)[1] as stellar, I reference and use it all the time and have genuinely been happy with it.

To be fair in assessments, I’ve also found links in Microsoft’s documentation that often link to things they have already marked as outdated or not going to be updated, or just don’t work like the GitHub links on this page:

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-...

So I think a lot of documentation around the big platforms especially have a lot of work to do. This isn’t to say documentation is easy though. I sincerely hope that all this noise just means it becomes more of a priority. I know from experience that writing good documentation is hard and I don’t want this to come across like I’m faulting anyone in particular or organization in particular. I imagine with large and ever changing platforms it’s quite the challenge. I just wanted to point to some examples I believe get it right most of the time.

[0]https://docs.python.org/3/

[1]https://developer.mozilla.org/en-US/
Besides the fact that the internet was already around by 1985, and e-mail and Usenet groups were a known thing in nerd circles, in France a network for the masses, Minitel, had already been rolled out. Jobs was not so much prescient as simply aware of what was going on around him.
Gamers for Freedom Is a New Group Pressuring Activision-Blizzard about Hong Kong
Most of the time it seems like a question is complicated only if you realize that what you are doing is wrong, but it makes you a lot of money so you don't want to change.

One example, Ocasio-Cortez asked: Can a politician lie about Election Day on a Facebook ad?

The answer is clearly yes. It isn't complicated.

Or this one: Does Facebook see a problem with its lack of fact-checking capabilities?

How can the answer to this be anything except yes?
HBO is not a great reference in this case. The teams of experts from the UN and WHO said "up to 4000" using conservative models after decades of study. One small Ukrainian team said 90,000, and that's the number HBO and Greenpeace use. Actually HBO said: "Between 4,000 and 90,000", which really pissed me off. The scientific consensus number is up to 4000.

https://www.unscear.org/unscear/en/chernobyl.html

The crazy thing is that even if it was 90,000, nuclear wouldn't change much in how safe it is relative to other energy sources. Again, Banqiao dam killed 230,000 and fossil kills 4,200,000 every single year from air pollution.
Sorry I don't understand your question.
> 1. It neglects dividends.

True, but if I replaced S&P500 with VTSMX (a Vanguard index fund, which got marginally higher than 50% returns over the same time period) would not.

> 2. The S&P 500 as presently constituted omits all the companies that were excluded during that time period (eg., went broke).

The current S&P 500 does, but watching the S&P500 index over time does not. And index funds generally rebalance to take these things into account.

As another user mentioned: knowing which companies are "good solid companies" is a trillion dollar industry. No simple strategy beats the market over the long term, other wise passive investors would all do it, and start beating the market.
It is part of the Swift project, but it is not really part of the Apple development ecosystem. It might at some point be, but it is not now, and it is a small side project. And it is not, in general, used when developing for the ecosystem.

And you may feel that way about docs, but it is not reasonable to find one single rushed release, and use that as an argument against the entire ecosystem. That is not a reasonable argument.
I've written several pieces of code that I am quite fond of. I guess the most recent was last year. A client asked what was necessary for a totally secure yet extensible blogging system. I ended up putting something together in Vue.js and AirTable that was tight, static, and extensible. That had a sweet feel to it. It was extremely small for having so many features. Fun times.
Official documentation may be more important for a framework that is new, especially if it's one that developers are being required or encouraged to switch to.
Man wins French Scrabble championship without speaking a word of French (2015)
I don't agree with this article and this culture of making failure a beautiful thing. A Failure is a failure.

When people fail, a lot of things go bad. Many of them get depressive, they go through a lot.

It's like saying that having abusive parents make you a strong person. Completely bullshit.

I doubt this has any positive effect on "setting somebody up" for success. It is much easier to be successful if you don't mess it up. For most of the world, people aren't even allowed to fail once.
That’s the reality in most companies.
>Looks neat but I don't know why you'd choose it over one of the big 3

Vue is backed and influenced by Chinese corporations, and React is FB, if you dislike both and can somehow afford to avoid depending on them you might become a happier dev.
But Chernobyl was in the Soviet Union. This was considered not the west, right?
I'll keep that in mind because I actually prefer learning from books. What's really interesting is that the rules of the system come from nature itself. So by knowing how a computer system works from the point at which its components interact with the physical world to how the software works would give you some kind of technical mastery that has to be good for something.
We are in a dark age at the moment, is what I am saying, and I think we should be working at getting out of it.
Go Is the New Ruby
>> One is a developer reaching out (costs: developer time, management involvement: granting permission). The other is a change in project plans, staffing, workflow and timelines (costs: large, management involvement: massive).

I think it's a pretty safe bet to expect, for this reason alone, that the documentation quality of things like SwiftUI will improve over time. It seems pretty obvious they directed all their efforts to releasing SwiftUI within their iOS 13 release window, which likely meant the API only 'stabilized' very late in the process and it would be impossible to spend time and resources documenting it, at least not without postponing the release (not an option).

Generally speaking, in my experience all of the 'established' Apple API's have pretty good documentation. SwiftUI seems rushed, and it would probably been better if they waited until iOS 14 and release it along with documentation. I'm not definding Apple here, but I think the article is overstating how bad their documentation is based on one brand-new API that probably wasn't fully cooked for release to begin with.
> The "collective intelligence" of the market has obvious blind spots.

As does the collective intelligence of the voters and the state. Whichever is more, and more consistently intelligent is apparently not obvious.
Could you elaborate on Crowdstrike?
It always surprises me when people remap the caps lock key. I find that I use it quite often.

For vim you case use 'C-[' I believe which does the same thing as escape.
I'm generally for heavier regulation vs. rampant capitalism, but regulating what media companies can & can't do with their content isn't the answer. That feels like it'd be heading down the path to a state run media.
IME skill-stacking (and including something rel to people / human interaction in your wheelhouse) is the best path to [power / authority / autonomy / clout / leverage]. It doesn't have to be binary "tech or mgmt". But you're absolutely right; companies are groups of people. If your role is such that your influence doesn't extend beyond what you can personally code, your sphere of influence (and career opportunities) will by definition be limited. This can be mitigated by eg explicitly developing skills of presentation and persuasion... but if you work somewhere that has other employees, and don't want to get stuck in a downstream role slinging code, there is no alternative to learning and mastering the [human] interface to the rest of the company.
I know that when I secretly test weapons, I do it in a way that makes sure the effects will be in the news 24 hours a day for weeks and months.
There should be a Step 0 to indicate that every product idea lives or dies on the degree to which it can be tied back into Google Ads.
How did (e.g.) Apple II pricing compare to equivalent-ish, contemporaneous models from Commodore or Tandy?

Apple ][: $1,298

Commodore PET: $795

Tandy TRS-80: $600

At these prices, in 1977, only the Apple had color graphics.
Same. I'm 38, and I've told my 7 year old that I would expect that her grandchildren's generation probably won't need drivers' licenses. I think that period from about 20 years from now until then will be a somewhat uncomfortable overlap period where people will still need to know how to drive, but that computers will be doing more and more of the actual day-to-day driving.

The only thing I could see that would shorten the interval is legal approaches. Such as, if the technology proves sufficiently adept, for it to be declared as a mandatory safety feature on par with seatbelts and airbags. But even then there will still be non-autonomous cars on the road (just as there are still cars on the road without seatbelts and airbags) for many, many years. Again, unless you take the extra legal step and ban them from the road.

That doesn't mean it isn't worth doing. Something that we fail at a lot in the modern world is thinking long-term, beyond our own lifetimes. Just because something might not get done during my lifetime doesn't mean that we shouldn't do it, just that others may have to finish the work we started. Ultimately, society will be better for the investment we are making now.
Potentially, but just because people aren't doing the 100% most altruistic thing all the time doesn't mean they should be shamed for doing something that seems, at worst, neutral to everyone else.

"What if rich people gave away all their money to causes I support" is almost always a valid position, but one that doesn't really help advance any discussion of the merits of any other action that's more viable.
Which is still leaps and bounds ahead of today's C-level exec
"The greatest potential loss in our relations to machines is not runaway GDP or disinformation, but rather the existential right to enjoy the surprise and uniqueness of human effort." This is similar to the "Artist's Lament" described eloquently by Feynman (https://www.goodreads.com/quotes/184384-i-have-a-friend-who-...).

Actually, it would be very interesting to read fiction created by an AI that illustrates what it means to be a machine, similar to how we are recommended to read works written by people from other cultures. Note that the AI does not do this: as the article states it's trained on "more than 40 gigabytes of online writing", so it's just holding a mirror to what humans have written with no insight into "machine-ness". This is is like picking up a Chinese writer and finding out that it's a story about the Midwest, written in the style of American storytellers. It may be even called cultural appropriation (see different writer's viewpoints on cultural appropriation: https://www.theguardian.com/books/2016/oct/01/novelists-cult... and Zadie Smith's eloquent push bak against it: https://www.nybooks.com/articles/2019/10/24/zadie-smith-in-d...). OTOH, if the AI's fiction is truly authentic we may not be able to understand it a la Wittgenstein's lion (https://wittgensteinforum.wordpress.com/2007/06/13/wittgenst...) because it will be far removed from human experience.

Why do we read fiction, though? If the answer is for it to be "an axe for the frozen sea within us" (https://www.goodreads.com/quotes/237620-i-think-we-ought-to-...) then we don't care who generates it: if an AI has created a story that moves you, so be it.
Huh, interesting. I never knew anything about that. That said, I use cert-bot, but not only certbot, as I have a wrapper script which does some other things as part of the process (converting the certificate to Java Keystore format, for example) so not sure if that automation would apply.

Anyway, my script is setup now, so hopefully this won't be a problem going forward.
Driver development docs on macOS largely haven't been updated in 10+ years. I started doing macOS kernel stuff when Snow Leopard was the latest release, and the only documentation I can think of since then has been sample code for Audio Server Plugins (for writing new-style audio drivers) and headerdocs explaining the transition from IOUSB* to IOUSBHost* APIs. Any additional information has been buried in a bunch of WWDC session videos, or you have to extract it from Apple by filing DTS incidents.

On the other hand, Apple have decided a bunch of documentation was out of date, so they've simply made it harder to access by burying it in archive sections or taking it offline altogether, without providing replacements. Getting into driver development now is almost certainly a lot trickier than it was back then.
tl;dr the census accurately counted a deficit of millions of people, so the census takers were executed. There is no telling how many of the "before" count had existed, as previous counts were systematically inflated.
One raspberry pi for all! The devices are connected via zwave wireless with a USB stick zwave controller. Actually I moved the main server from a pi to my home server a while ago but it was all working fine on a pi 3.
"Just don't steal my stuff"

- Everybody that uses this quote
I don't think I use any machinery. All the equipment that needs any cleaning that I use is a bowl, spoon, silicon spatula, dough cutter, and a silicon baking pad.
Thanks! That was one of the biggest challenges.

There are several good data sources, such as the official ATP website or Oddsportal. I managed to fetch data from these sources and centralize the info by matching keywords such as the players names.
You wroye this:

,,What about the government policies regarding recycling or waste management? Or consumer behavior regarding waste?''

The problem with consumer behaviour change is that it doesn't scale. There are billions of people who pollute much less than an averahe person living in US, but they are unable to offset it

Blaming doesn't need much effort, so even though it has less direct effect, it can scale better through social media.

Regarding government policies (and especially enforcement) you are totally right though.
You could just stockpile long shelf-life foods and literally save today's production for future consumption https://www.offthegridnews.com/off-grid-foods/stockpiling-10...

> You need actual future goods production.

That's the real key to "world savings", and in your terms you can think of it as "making youth more productive" (or making the elderly productive enough).

In the desert island, You seem to imagine that labor is a zero-sum game (the desert island is the same tomorrow as today) rather than a positive-sum, where I improve the world by my labor, in addition to providing for today's consumption.

Imagine an isolated homesteading family with no community. How would this person/family save for old age? By building up the farm, building tools, planting orchards, building irrigation systems, managing forests, so that today's labor can reduce the amount of labor required for the future.

Agafia Lykova is such a person - https://www.businessinsider.com/72-year-old-hermit-lives-in-... - she lives alone, using tools saved from an earlier time, in a home her family built in previous decades. Life with this infrastructure, including maintenance, requires less effort than initial construction, which was done when there was surplus labor available.

Similarly for a country or a world - the net savings exists in acquired infrastructure (capital) that enables future production (& consumption).

Trees are a good example - by planting fruit trees (capital investment), I enable future fruit harvests. Managed timber forests provide future lumber (or fuel) production decades later.

Similar investments in infrastructure (water systems, equipment, buildings, etc.) all represent net saved value today that enhances future production in subsequent years.

Yes, labor is required in future years, both for production and maintenance (unless/until we can fully automate), but the ratio of consumption today to future consumption is not constant, even in global sum (e.g., the years 1940-1945 may have been a world-wide net loss of acquired capital, certainly for Europe). That net improvement in infrastructure is global savings (or loss).
It is powered from the same circuit that powers the doorbell chime coils.
I'm extremely comfortable reading documentation for a very wide variety of platforms, languages, etc. (The first software I ever wrote was Fortran via `gfortran`. Trial by fire!) It's not just me. This is just straight-up absent: https://nooverviewavailable.com/swiftui/

As I noted in the post, I'm getting by anyway… but it's more work than it needs to be, and more work/worse state of docs than other ecosystems I've learned in similar amounts of time.
Chaos bei Produktdaten? Sie brauchen eine PIM-Lösung
I'm genuinely curious; how often do you actually end up writing sorts in Haskell? I just use the built-in sort function, which is fast enough.

Maybe your use-case is different than mine, but I typically use Haskell (or another functional language) for network applications, which typically don't benefit from tight-loops since the network is almost always the bottleneck anyway. For these kinds of applications, having proper concurrency and IO handling matters a lot more than worrying about whether your loops result in a cache-miss.
To give you an idea of how underreported this chapter in computing history is...

I was born in the 1970s and grew up in the 1980s. Huge computer nut since an early age, devouring computer magazines many years before we even owned a computer. Used Apple ]['s in school and knew which game consoles used 6502's and their descendants.

And I still had no idea that WDC was based a few miles from where I grew up.

I learned that only a few years ago!

From a local perspective, perhaps this is because they promoted themselves as being based in historic Valley Forge, PA. When in reality, they were based in nearby Norristown, which is kind of a downtrodden town and obviously lacks the name recognition of a national landmark like Valley Forge. I'm sure Norristown would have loved to trumpet their role in the computer revolution, but that would have been tricky to reconcile with MOS's (understandable) claim to actually hail from the next town over. Awkward!

(....or maybe it's because MOS left behind a superfund cleanup site....)
The Swift language has excellent documentation.

For SwiftUI, the WWDC presentations are essential, IMO, for the high-level stuff. There is basic reference documentation, but there's no way to put it all together without a high-level understanding. It follows the patterns of some other frameworks so depending on your experience you may be able to get by without the WWDC presentations, but I'd still watch them or at least read the transcripts.

I think Swift Package Manager is meant as a community tool, and the love and care it needs to become excellent is not going to be coming from Apple, not without some kind of strategic change. Either the community will value it and figure out how to move it forward or it's not going to get much better. I could be wrong -- I'm trying to judge it's on-going strategic importance to Apple -- but I think the way it's going to improve is through community involvement.

Anyway, I'm not sure what the point of this kind of rant is. Whining about Apple is an easy way to get useless internet karma points, but it's such a bad look for a developer. At least half the job is being the one who finally deals with things someone else probably should have already dealt with but didn't.
My experience has been that the value of very senior technical staff is not that they solve "extremely high level" technical problems but they are very easily able to see how what appears to be a complex problem is isomorphic to a much simpler, easy to solve problem.

The difference between expert and advanced/intermediate technical staff is that the advanced engineer has an understanding of complex solution and mistakenly tries to apply them everywhere, so the net effect is to increase complexity. The expert typically sees simple solutions and method of resolving complexity and has a net effect of reducing overall system complexity.

Believing that the value add of experienced technical staff is to only solve really hard problem is likely caused by having too many advanced/intermediate people playing the role of experienced technical leads. All of the great technical team member I worked with always make call solutions simpler and easier to implement by knowing exactly what doesn't need to be done and what is essential.
Apple wiped 20M ratings last week
php, whether you like the language, or abhor it, has always had some of the most useful documentation, I've found.
Why are retirees expected to have such high incomes? I fail to see why 50% or less of their incomes isn't enough. Not trying to be difficult, it just doesn't match my blue collar parents' experiences. Most peoples' expenses in retirement basically amount to either property taxes or rent, healthcare, and food. And Medicare kicks in at 65, Social Security around the same time.