skysight-inc/HackerNews huggingface dataset:
Bugzilla is also pretty awful (and I say this as someone who uses Red Hat's Bugzilla instance hourly in my job).
It’s important to understand the importance the homesteading act played in the civil war. It was signed into law on the same day as the emancipation proclamation and together represented Lincoln’s resolve to preserve the west as a place of freedom and opportunity. Signing the act essentially removed any hope of southern control of the west because it recognized the property rights of squatters in the west and gave them title belonging to the Union rather than the confederacy. It also galvanized numerous factions in the North to support the idea of total victory when they might have otherwise agreed to a compromise. The economist Hernando de Soto points to the homestead act in his book the mystery of capital as one of the defining ways in which the west, formalized capital and built massive wealth by recognizing the property rights of participants in the informal economy.
I definitely see the desire to replace Objective-C, but the downside of ABI stability seems to be that it prompts a lot of worries about new features or optimizations affecting it. I hope this won't add too much sand in the gears.
Hungarian notation solves one problem: it makes wrong code look wrong.

Type alias can also do that, but they can do so in a way where correctness can be statically enforced.

As an example, let’s say you have a Write function like in the article, but it only takes an HTMLString, which can’t implicitly be casted from String. Then, you can have Encode return an HTMLString, but take a String. Finally, you can use static analysis to only allow whitelisted functions to construct non-literal HTMLStrings (so anyone could do a literal of HTML, but every other usage would require encoding or whitelisting.)

This is a bit rudimentary of an example, but it is widely used in practice.

Here is a safe type used in Closure:

https://google.github.io/closure-library/api/goog.html.SafeH...
Which is basically what I said in https://news.ycombinator.com/item?id=21490182 Never put up barriers to accepting bug reports. Now does Trac help in any of this? No.
Thanks for this, haven't seen it even though I've been actively searching!

I think it's hard to get taken seriously by companies when you sell a "script" on Invato too and I'm not sure why they do this? Why not just sell it yourself and receive more of the profits?
Not the rejects, the prudes.
> He hopes to have a clinical trial within the next three to five years.

It's been just over 4 years since that article. I wonder what has happened since.
The main problem with this challenge is that a) most Swift developers are more used to writing front-end code and b) the specific network card isn't available to everyone that would like to look into this problem (like people with MacBooks). So while this driver seems to spend 3/4 of it's time in retain/release and I see the word `class` everywhere and the word `inline` nowhere (while inline is used in the C version it's based on!) I just can't do anything to improve it's performance.
Search "WebKit dfg" = https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/

It's a layer of their JS pipeline.
I loved the combined view of reminders and email that 'Inbox by Gmail' used to provide, in the lack of a more sophisticated solution by GMail, I just email reminders and Snooze them to the appropriate day.

This little hack works really well and have given me decent mileage.
What changed I guess is that they switched to embrace Linux full on. And now extending it as well. I trust that Linux is safe from extinguishing though - too much of the world runs on it, and free servers are just too compelling.
It's also the only legal option for the audience to take. The companies who own the copyright make the content available under certain terms. Don't like the terms? DON'T WATCH THE FUCKING CONTENT. If you do somehow contrive to watch the content despite not accepting the terms, then you are stealing and will be prosecuted to the fullest extent of the law. Capisce?
Didn't realize the Linux version was offered through the official channels. That's something.

Still, to truly compete it would need to have Windows support too. And ideally real buy-in from at least one other major tech company.
Service Worker is the first step - they need to catch up there first. It’s on the list!
Have money back guarantees helped your sales?
How will they force you into the $99/annum developer program, shaft you a cool 30%, play judge and jury to your ios, macOs app store submissions and reject your work at the first hint of competition, if all the useful PWA features just work on iOS? Lest you dream of software freedom on Apple devices, their sycophants and overzealous employees will gaslight you into believing it's all for user experience and security, and any incidental monopolistic/anti-competitive byproducts are wholly acceptable collateral damage when the betterment of iKind, ahem, mankind is at stake.
Still, we have pediatric cancers that are not caused by lifestyle. I wonder what's the ratio for small elephants. Are the also more protected ?
Library can't provide backwards compatibility or even any compatibility if newer version of compiler decides to change the layout for a structure or an enum thus breaking ABI for everything including parts of library that didn't change.
I get a black background on the world editor page https://hordes.io/worldeditor

Console output:

public_editor.js?v=2939736:9148
Hordes 0.26.2939

public_editor.js?v=2939736:9152
Entering state: play

worldeditor:1
WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost

Edit: nvm I get a black background in the game too T-T I can still walk and turn the camera, though.

client.js?v=2939736:24217 Hordes 0.26.2939

client.js?v=2939736:24221 Entering state: play

client.js?v=2939736:24113 tried ws disconnect, but ws undefined

client.js?v=2939736:24116 connecting to game server: hordes.io:5002

client.js?v=2939736:5723 connection opened

play:1 WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
An old video [1] in response to this old article may indicate another reason why elephants dont get cancer, and provide easier way to replicate those results than gene therapy or splicing. Hint: go vegan.

[1] https://nutritionfacts.org/video/how-not-to-die-from-cancer/...
Trac is better than the GitHub/Bugzilla model, in any case, in my opinion.
Not extinguishing perhaps, but appropriating and building upon Linux for their own benefit without giving much back is certainly possible. Google's already done it with Android.
Yes that's right: ABI stability is all about nailing down which changes are "backwards compatible."

In C++, you might wish to add a field to a struct, or add a new virtual method, or change the inheritance hierarchy, or the type of a parameter, etc. But such changes are not ABI compatible and will break every app until they are recompiled. The C++ ABI compat story is very strict.

Modern ObjC has a more generous policy, leveraging its dynamic nature. For example you can add fields or methods to classes, without recompiling dependencies. But you pay an optimization penalty, since the apps have to defer offset calculation until runtime.

Swift attempts to have its cake and eat it too. Swift enables you to be explicit about which types might change in the future, and which types are "frozen" and can be aggressively optimized. Furthermore you can explicitly draw the ABI boundaries are: THESE parts are always compiled together and so intra-references may be aggressively optimized, but THOSE parts may need to evolve separately so enforce an ABI there.
Company Retreat

What?

=> A company retreat is a better way to connect with your colleagues outside your official environment which helps your teammates to express themselves which helps the whole team, which is what you call as a company to prepare for the next small/big changes the company would be planning ahead.

Why?

=> It creates that bonding within your team and changes the perspective towards their project/work on a positive note.

=> For eg, if you are changing your strategy or developing a new product/idea, (works very well for ideation I hop), a company retreat would be really useful to make sure that all are on board and aligned towards the goal.

=> It improves the morale, better bonding, communication skills and especially the considerations & cooperations.

How?

=> Letting your ego's go would be a nice way to plan it out. Collective decisions and plan it out :)
I believe I've read this verbiage around cancer in pets, such as domestic cats living far longer than "intended".
Well yes to this - in the 80s you were either System V or whatever crap IBM was selling back then! :)

Ps I always assumed 80x24 was a teletype (eg. tty) standard or at the least a two-by 80x12 punch card layout. I also wonder if the serial cable throughput to the terminal played a role..
Why does using the proper definition of words matter? I think that should be fairly obvious.

"Downloading copyrighted music is murder."

Ok, then downloading copyrighted music should be punished like murder.

Oh, it isn't Murder?

Well, it also isn't theft. So it shouldn't be punished like it is theft or treated like it is theft in conversation. It should be punished like and treated as copyright infringement, which it is.
I'd like to see many more web sites have info about google's non-transparent censorship prominently displayed like this guy put together - showing alternatives for big G's products.

Maybe there is good reason for the harsh removal of this guy's site (even ruining the site:his-site searches! ouch) - Maybe someone manually hit it for quality 'your life your money' stuff and combined with the strict algo and so it's technically following the trust rules or whatever - that's not for me to judge at the moment.

The bigger issue imho is that there are many of these de-rank and de-list things happening and it's not transparent to the end users.

So many people have come to trust google to give you what you search for, and for years they have the Gplex has been cutting up more and more pieces of the internet to remove from their index - and there is no transparency about this.

So many people think everything on the internet can be found via google, (and some thing whatever is on fbook is the internet and know nothing beyond what is / can be shown there ) - if things are censored there, they likely assume the things don't exist.

I don't mean everyone, but I'd wager most people.

There were times when I have seen google put a notice at the bottom of each page of certain searches with something like "some results are not shown here that once were shown here due to chilling effects of legally mandated takedown requests" - click for more info..

So to me, that was snarky transparency - I think attempting to nudge people to try advocate for change with dmca forced censorship of google. Maybe I'm wrong in seeing it that way.

Anyhow - there was transparency when they were forced to remove listing for, was it movies? or movies and music and such mostly?

Yet we are not seeing transparency about removing listings such as the one this mercola place is mentioning that was shown and people visited, and many others.

I think most people don't even bookmark or otherwise save pages these days, assuming the "address bar" which has basically been hijacked by google search for most people - is going to re-find the info they had seen previously - or heard about from other people.. and now that info may have been shadow-banned essentially - and poof - that never really existed in the world.

This is the reason I think the reliance on google is more evil than fbook - at least with fbk they are more transparent about censoring many things.

The more places and people that post about the censorship and alternatives that are out there, the better I believe.
I think this is an excellent observation and I agree that it's very hard.

I'm no expert whatsoever, but I think that the key to all of this stuff is nuance. Nuance, nuance, nuance. Nobody's totally good or totally bad, and you just need to dig deep enough to see the details. A jury can see all the nuance (if there's enough lawyer time/money to dig it up). A judge can (eg in contintenal European courts).

Here in NL there's a popular narrative that judges are old rich white dudes who are disconnected from reality (they're actually mostly middle-age white women, but OK). I never understood that narrative - these are people who get confronted with all the nasty parts of society in their full nuance, all day every day. They see that somebody commits wellfare fraud, but they do it out of desparation to keep their family afloat. They see that someone beats up their wife, but it's driven by harsh inescapable alcoholism. These are tragedies plain and simple, and it's extremely hard to just say either "you were just a victim!" or "lock you up forever!".

Personally I think mob outrage (eg on Twitter), or justice processes with too little money for proper lawyering, are a serious threat to society precisely because of this. If there's no time or space for nuance, everything becomes black&white and tragedies deepen.
Robocall on the Fly with Python – ___
Asking for clarification is one thing, immediately providing a counter-example to the most literal interpretation is another.
I think the misstep by Apple was to focus so heavily on iPhones that they stopped paying attention to the developer experience on Mac. Look at the fucked Catalina release, the slow MacPro update cycle and the abandonment of the Mac Mini, the obscene SSD pricing (especially combined with the way Docker likes to eat gigs...), and yes, the shitty Macbook Pro keyboard and stupid touch bar. Lots of things that together add up to a poor developer experience.

Obviously, Mac doesn't need a subsystem for Linux because it's already a *nix and all the tools work there already. Microsoft was playing catch up, but they're starting to look pretty well caught up.

Now, this isn't to say Apple is doing poorly, obviously they make ungodly gobs of money and are usually the most valuable company in the world. My original comment was about developer mind share, though, which I think is swinging back towards MS after being thoroughly owned by Apple from, say, 2008-2016. By not making the developer experience a priority, I think Apple is losing ground that they didn't have to cede.
That's an explanation of how users can allow notifications, not why they should.
You need to understand that many of us like Apple's approach.

We aren't looking for software "freedom" on our phones. We just want apps that are safe, curated, respectful of battery life and do not infringe on our privacy or user experience. Apple's approach gives us that.

So by all means complain about app store submissions but as a developer I don't have sympathy for other developers who play loose and fast with the rules.
I guess you could walk the stories API, extract all the user IDs, and then enum those through the users API to get the Karma values, and then run stats on that... it's a big effort, and I'm not sure what the useful payoff would be.
IBM uses Swift for mobile apps https://developer.ibm.com/swift/2015/12/03/introducing-the-i... and develops Kitura (https://www.ibm.com/cloud/swift), a Swift web framework.
tree-seq
Man, I wish Microsoft was paying me, but I'm just a guy who uses OSX and Windows 10 (and Linux) regularly and doesn't have much of a dog in the fight.
What changed is Azure and you can be sure they will do what they can to keep you locked into that ecosystem.
Please notice the usual wisdom of PostgreSQL developers "(8GB in a standard installation)" meaning they probably set up a config parameter that you can tweak if you ever reach this limit while scaling.

This is an often untold superpower of PostgreSQL when arguing about how it supposedly "don't scale well". You often have a large array of optimizations available before your project really scale out of scope.
Currying is just another example of poor abstraction. You have a function which returns another function which may be passed around to a different part of the code and then called and it returns another function... Abstraction doesn't get any leakier than this. It literally encourages spaghetti code. I despise this aspect of FP that the code ends up passed around all over the place and keeping track of what came from where is a nightmare.

I've written plenty of very short OOP programs. They don't have to be huge to be effective. The reason why you sometimes see very large OOP software and rarely see large FP software is not because FP makes code shorter, it's because FP logic would become impossible to follow beyond a certain size.

My point about black box and referential transparency is that a black box hides/encapsulates state changes (mutations) by containing the state. Referential transparency prevents your function from hiding/encapsulating state changes (mutations) and thus it prevents functions from containing the state which is relevant to them; instead, the relevant state needs to be passed in from some (usually) far-flung outside part of the code... A part of the code which has nothing to do with the business domain which that state is about. To make proper black boxes, state needs to be encapsulated by the logic which mutates it.
Embraer E175 Loses Control over Atlanta
in some countries you can though, even if sentenced, so it's not a dumb question. The idea is that after, say, 15 years (jail or not,) you've been rehabbed, making jail moot.
as is tradition already, webkit is missing:

- full PWA

- ServiceWorkers

- VP8/9

- webvr

- and many others

this could all be mitigated if aapl would let us install custom non-webkit browsers on ios. unfortunately it seems we will need the courts to force aapl.
Hacks like this work at first, but long running transactions and postgres don't do well together.

After a few weeks of running on a multi-TB table, you'll find the dead tuples massively outnumber the live tuples, and database performance is dropping faster than the Vacuum can keep up. Vacuum is inherently single-threaded, while your processes making dead tuples as part of queries are multi-threaded, so it's obviously the vacuum that fails first if most queries are long running and touch most rows. Your statistics will get old because they're also generated by the vacuum process, making everything yet slower.

Even if you can live with gradually dropping performance, eventually the whole thing will fail when your txids wrap around and the whole database goes read-only.
You never "artificially cap it to protect against stack overflow": Most libraries that cap it artificially cap it to a fixed value, that may or may not protect against stack overflow depending on how large the stack already is when you call the parser.
Confusing. Foreign keys are a vital part in RDBMS and very useful. He is talking about foreign key constraints, which can be problematic as described.
I've had similar success with the gradual typing in Python. NamedTuples are far superior to ad hoc dictionaries, for both documenting data structures, but also as a prompt to consider the software structure.

I wasn't aware that typescript type errors were only warnings. Every webpack/typescript project I've used must have had the typecheck set to error, leading me to believe typescript was some draconian type checker akin to Rust or Haskell.
And one of mine already jiggles and has unreliable connection because of stress. I've cringed when I accidentally yanked my computer not realizing it's charging or connected to something else.

My next macbook, I'm definitely buying those 3rd party magsafe-like dongles that sit in my usb-c ports!
Yep - opening up W3C PWA standards on iOS may really threaten "safe, curated, respectful of battery life and do not infringe on our privacy or user experience"

That's just science, and not a regurgitation of Apple's excuses, ahem, P.R. on the matter. I mean, just look at the devestation unleashed by chrome (which supports all PWA features) on MacOs.
Here's a site I made with a legitimate use of Web Push. https://james.darpinian.com/satellites/
Sorry, you are correct, I was imprecise.

"ABI stability" is about defining an ABI. "ABI resilience" is defining how libraries can evolve in a binary compatible way. Stability is a precursor to resilience.

Apple would like to write libraries in Swift, but those libs have to participate in an ABI that is stable (so apps can use them) and resilient (so Apple can evolve them without breakage).

> For new UI backends you don't need a different interface, you provide the new UI under the old interface

The challenge is how to provide new UI features without breaking existing apps. For many UI frameworks (the web in particular) the compiler/runtime has a global view and can sort it out. But if both the app and library are separately compiled, the problem becomes trickier.
Quite a lot of Google-developed code goes back into the Linux kernel. Look at cgroups - the entire containerization revolution sprung from code Google gave back to Linux.
the path to glory is a long and arduous one
We don't know if (all) cancer can be cured at all.

And no, "in time and budget" doesn't suddenly make something into a research project.

Speeding up some technical process might be research (eg, the old 1TB sorting benchmarks drove research).

But project constraints, and the fact that the team themself has never used a specific technology or whatever doesn't turn it into research. Yes, I know that's a term people use, but it's a different thing to scientific research.
I tend to think libraries work fine with Go. It's "frameworks" that are difficult.
No PWAs, no proper service workers, no native lazyload, no WebP, always lagging behind with more buggy implementation of almost everything. Can't blame people who call it the new IE6/8.
Can you recommend something to tie FIDO2 to generic web applications that don't support it directly?
Django still uses Trac. https://code.djangoproject.com/query

It really is awful.
Nice work! Tested it and it looks promising for simple web apps that require minimal native APIs. What happens if the user does not have Chrome installed?
That incremental reduction in friction converts to substantial financial gains, being on the app store.
to each his own, but most, if they can, do have children. Those with genes that don't want to have kids went the way of dinosaurs.
Personally the problem is not that I don't like it, but that I have no way to test against it. No, I'm not buying their overpriced crap just to see what they've broken for their users.

Even MS has had modern.ie[0] for years. Until then, Safari users are on their own[1].

[0]: https://developer.microsoft.com/en-us/microsoft-edge/tools/v...

[1]: https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html
> Am I understanding correctly that readers' performance will degrade by the same amount?

Not quite. The "slow path" talked about is only applicable when the coordinator node is unavailable (presumably a rare event). If it's unavailable, there's nobody left to clean up the STAGING txn record, so the reader is tasked to do it itself.

In normal conditions however, once the coordinator node receives acknowledgement for the successful persisting of all write intents and the "txn STAGING" record, it can simply record "txn COMMITTED" in memory (and return to the client, send off async intent resolution procedures, etc.) Any subsequent read requests that observes left over intents (yet to be resolved) are pointed to the coordinator node, which can simply consult the "txn COMMITTED" record in memory. This is all safe because the commit marker is not simply stored on the coordinator node, it's a distributed condition and can be reconstructed by any observer even if the coordinator failed.
So instead of getting a permission prompt on load, I will get it when I first click on something. No thanks.