skysight-inc/HackerNews huggingface dataset:
Faster, generally easier, cheaper (in terms of start-up time).

I have no problem with choosing between GUI or CLI interfaces, but I find myself doing far more work via the CLI than with GUI.

My desktop is comprised of several (usually 6) virtual desktops with both graphical apps and CLIs (xterms of various sizes) liberally placed thereon.

As such, there is no obvious incentive to use a GUI and no obvious incentive to use a CLI. I believe I tend to use the right tool for the right job. So it is natural to start up a GUI app when images are required.

When it doesn't matter whether a particular image is supplied, I generally use a CLI. Because I don't need to 'fire up' yet another standalone program, it's 'cheaper', both in effort and also in start-up time, to simply use the nearest xterm.

In effect, one xterm can take the place of maybe half-a-dozen different apps, as well as being more convenient for me.

Jobs which need to repeated more than once a week can be stored as CLI scripts which can be invoked with a single word or, better again, called by 'cron' automatically. Try doing that with a GUI.
https://www.postgresql.org/docs/current/sql-notify.html

> There is a queue that holds notifications that have been sent but not yet processed by all listening sessions. If this queue becomes full, transactions calling NOTIFY will fail at commit. The queue is quite large (8GB in a standard installation) and should be sufficiently sized for almost every use case.

My understanding of MVCC (correct me if I'm wrong), is every time you do an update, dead tuples are left behind that need to eventually be vacuumed. If vacuum isn't running or can't keep up, you'll run out of space or have a tx id wrap around.

Work queues are a simple paradigm and swapping out one queue for another is a trivial exercise that won't change the architecture of a system, and SQS or PubSub could be easily used, regardless of where the rest of the project is hosted. I'd rather pay that one-time cost than the ongoing cost of maintaining my own job queue service and infrastructure.
Changing your country of residence when you get a new job is perfectly normal. Changing your nationality is not.
Is the use of stenography related to the liberal use of commas in your comment?
You expand horizontally, by adding new pages and slowly creating content that ties back to your new offerings. You keep the keyword density of your main SERPs unaffected and try to do a minimal integration of new links targeting the pages you want to rank for new search queries.

Their mistake was destroying their relevance with a big bang change. If your website ranks generally well for a term like "logo creation tool" it's because you did some work to build the authority against that keyword. But if you decide tomorrow to change terminology around your business and redesign the without understanding the key content of your pages, you're going to affect relevance.

Google crawls your website today under logojoy.com and sees a lot of logo creation related keywords. Then it crawls a week later and sees a 301 redirection a shit-ton of changes and new terms, and potentially completely different markup with those changes. Of course, you're going to get a massive SEO hit. This was a poorly timed and uncoordinated strategy that resulted in this outcome.

If you change your domain name AND change the terms that you're targeting and add more vagueness to your content Google will re-index you differently. It's as simple as that.
>However, should you be able to share your Netflix username and password with everyone on the block?

Presumably, your Netflix subscription has limitations on how many people can simultaneously watch it. So, yes, you should be able to share it with everyone on the block. Why not? By doing so, you're potentially preventing yourself from using it during that time, for instance if it has a maximum of 4 simultaneous streams. Why should you not be able to use the maximum number? It's no different than having 4 copies of a book or Blu-Ray and lending them out to your neighbors: if they haven't all borrowed them, you still have at least one to view, but if they're all borrowed, you're unable to view them.
> because it somehow sexual (not being a native english speaker, I fail to spot the innuendo).

In the US, DD is a cup size for a brassiere, and thus indirectly refers to breast size on women. DD for sometime has been considered to be an uncommonly large breast size for a woman, especially a woman of otherwise more common proportions. DDD, being the next cup size up for reasons I don't understand (instead of cup sizes going E, F, etc), would therefore imply a woman even bustier than the supposedly uncommonly-busty DD-breasted woman.

Yes, I think it's silly, too. Human mammary tissue has exactly fuck all to do with programming.
Not a monopoly, but a walled garden.
SMS delivery reports
Is it even possible to realistically do FK checks in app code? Nobody uses serializable transactions and with other isolation levels I think it's possible to check for FK, it's OK now, insert new row, but another transaction simultaneously deletes that row and both transactions happily commit. It's called phantom read. Probably it's very rare event, but it'll happen.
Show me some evidence that suggests the current warming is something to be concerned about. Extraordinary claims require extraordinary evidence. And AGW is an extraordinary claim.
China is also another easy sample with Concentration Camps for Uighurs, Tibet ..etc.

[1]https://www.irishexaminer.com/breakingnews/views/analysis/wo...
[2]https://foreignpolicy.com/2019/10/26/uighur-concentration-ca...
[3]https://www.businessinsider.com/muslim-woman-describes-horro...
[4]https://en.wikipedia.org/wiki/Xinjiang_re-education_camps
Exactly. What Calvin (and FaunaDB, I think) does is allow you to run an arbitrary function which takes input on the database. That function can do whatever it wants, including any number of reads, writes, and arbitrary logic based on the reads. But critically, it can't talk back to the calling client, except for to send the final result.

This allows you to implement the pattern you describe, which I agree is common, but in a dramatically simpler way.

Having the database, which is not really a single thing, but a swarm of computers spread across the globe separated by unreliable links who are trying to stay in consensus, pause their work to hear back from the client just seems ... well it seems miraculous that it can work at all.

The Calvin way is so much easier, it seems like there must be some very good reason that it's not what CockroachDB does. But I've never heard what that reason is.
> So any time you want to get all the CHILDREN of a PARENT you have to query all children to see if they have a FK to the appropriate PARENT.

It's just an index lookup, so what? You'd rather mash all the data into a single parent field, is that it?
Apply anyway with a detailed resume about your experiences on projects, even your own.

The worst that happens is they say no :)
Any database that would let you disable constraints on a session basis is a toy database. Such an operation doesn’t even make sense because at some point the relational integrity has to be enforced for the entire table. You can’t just have parts of a table be relationally correct. That is like saying 1 + 1 = 3. It is a completely illogical statement.

However I would not at all be surprised to learn MySQL supports such a thing. Which supports my assertion it is a toy used (or at least installed by) people who have no understanding of relational database architecture.
Out of curiosity, do people only torrent, or is usenet still a thing? For the longest time, usenet providers would not log read access, only writes.
I find this to be largely untrue. There are certainly classes of algorithms and data structures that benefit from mutation for performance reasons, but at that point you can simply implement mutation in your pure functional language (e.g. with monads). Even ignoring that case, there are a great many data structures and algorithms that don’t meaningfully suffer from a lack of mutation at all, especially when the compiler is able to leverage assumptions from being in a pure language.

This is born out in practice where Haskell for example may not necessarily out perform highly optimized C, but it is frequently able to keep pace with Java and will almost always beat imperative python code.

In terms of being concise it’s laughable to me to even make the comparison. I’ve written a lot of C, Python and Ruby in my career in addition to Haskell, and Haskell wins on expensiveness to such an absurd degree that the comparison feels unfair.

The one area that I think FP, although really Haskell in particular, suffers is being to reason about. Performance and memory usage of course are notoriously hard to reason about in lazy languages, but it can also be challenging to understand what’s happening in large code bases that may have some deep MTL stack or be using multiple interpreters over some free monad, since the semantics of how computations are being evaluated can often be defined very far from the computation itself.
Yeah we definitely use recaptcha in a GraphQL API for sign-ups to browserless.io. There is a doc on how to do so programmatically via JS in the browser. The docs aren’t great, per se, but it is definitely doable.

EDIT: docs are here: https://developers.google.com/recaptcha/docs/display#javascr... though the lifecycle of how this all works is confusing. I’ll have to do a write-up on this at some point.
Speaking in terms of theory, it absolutely is. RDBMSs aren't magic boxes, they stage data for insertion, validate it, execute that insertion - all while littering the WAL (or equivalent) with the steps necessary for the guarantee of that operation. You absolutely can write this logic into your application, at that point your application may basically be Postgres but it's possible.

If you attempt this and don't exhaust a small rainforest's worth of notepad paper and a few truckloads of dry erase markers then you're probably doing it wrong - but the problem is solvable.

There are some unsolvable problems in this realm (like holding to ACID while also ensuring that all valid communications from a client are properly processed) but you can accomplish anything your RDBMS does, you just need to be really really absurdly careful and know what you're doing at a theoretical level.
This is all a bunch of BS. Apple didn’t ban the apps because they were using “web technologies” or even because they wanted “everything to be in the Mac App Store” but because they use private APIs. He even admitted that.

Seeing that “thousands” of developers are depending on a framework that uses private APIs that will take a long time to fix, kind of proves Apple’s point. If Apple releases an update that changes the behavior of the private APIs in unexpected ways - which they have every technical right to do since it is not a vendor’s responsibility not to change the behavior of non published APIs without warning, all of those apps will break.
Ok, let's just get one site approved, and all states that nuclear waste might travel through on board, simple, right? Why hasn't it been done then?

Regarding the volume of waste, would you feel comfortable sitting next to even a gram of raw nuclear waste? Even if the volume is small, it still needs to be handled with extreme care. If the handling of weapons waste is any indicator, that level of care has yet to be demonstrated.
I wouldn't say _all_, just most. With optimization, resource monitoring, disabling unused APIs, plenty of treeshaking and other such techniques, it's quite possible to do a near-native experience (think: performing like C#/Java).

However, whenever I see an Electron app in the wild, those optimizations don't seem to be done very often. Perhaps it's the fact that companies don't care about speed now that computing resources are cheap, or that companies are hiring web devs for desktop applications, but in the wild most applications sure do end up feeling like someone installed a buggy second copy of Chromium onto my machine.

Visual Studio Code is an example of an experience that feels like it might as well have been written in a language like C# or Java. With some extensions the lag quickly becomes noticable, but as far as text editing goes, it's a pretty nicely optimized tool. In my experience, typing in VS Code is slightly faster than typing in Jetbrains IDEA/etc., for example, which is based on the more desktop-oriented Java.

Of course it will never be as fast as Vim or Notepad++, but those tools are harder to extend, which can make the disadvantage of the slight input lag worth it for the extra functionality when debugging or running automated tests.

Electron can be a useful tool for writing maintainable, extendable, cross-platform desktop applications. It can also be a handicapped browser. While most companies choose to use it as the second option, this doesn't have to be the case.
In the UK this information is already published. They don't want fisherman accidentally damaging their assets.
Sure it works fine until you start multithreading, where handling an exception doesn't end with unwinding the stack, because there are multiple stacks. So then have to pass it as a value to some other thread's stack, and remember to catch it in every thread or else your thread will silently die. But then you're right back to where Go is: treating errors as values.
This is an odd article, brilliant in parts, somewhat less so elsewhere.

The analysis of why we need modularity and that this means we need new kinds (plural) of "glue" is spot on. Note the plural. But then he goes on to present exactly two kinds of glue, so the smallest N for which the plural is justifiable.

I contend that he was richt that we need a lots of different kinds of glue, which means that the glue must be user-definable. And what is "glue"? Well, architectural connectors, that's what.

Why Architecture Oriented Programming Matters https://blog.metaobject.com/2019/02/why-architecture-oriente...
A neat idea for sure. However I'd be concerned that suddenly you have two different applications. Example, if you delete a row with a cascading deletion elsewhere, that will work on dev, but on prod it would leave dangling data.

Though, I imagine you could simply not use cascading behaviors.. Neat idea though. Scary, but neat hah.
I give her more benefit of the doubt.

If you express strenuous disagreement and are in an officer role, when your "advice" is only treated as advice to follow or ignore, you have to take a stand if you believe in yourself. Because it's your head that's going to roll when this chicken comes home to roost. Better to go out with honor and preserve your integrity, in some cases.

Well, it's either that or she completely misjudged the position offered her. Seems gitlab didn't want an officer in this position but rather just a VP with an officer title.
It doesn't. Systemd-resolverd is a separate application, completely optional and only Ubuntu uses it by default.

Not that it is bad, but you don't have to use it.
> A primary job of the database is to keep itself from getting corrupted

That would be where the road splits. If you handle the database as a very fast and structured storage application, a lot of these assumptions go away, with then a different set of tradeoffs.

Some data corruption could be fine if you can guarantee the critical cases, just as bugs in the code are fine as long as the useful cases are covered.

I remember a database with scheduling entries in it that could get duplicated depending on the sharding, but it didn’t matter because the app handled the case gracefully.

I think understanding the tradeoffs that match the best the use case is the most important point, always assuming that a DB has to guarantee integrity can be a burden preventing from looking at all the options.
What was the solution for the SD card imaging?
What are you talking about? Electron apps don't run on iOS.
I've worked on exactly one project where performance concerns lead to removing Fkeys.

The compromise we came to was to enforce them in dev and qa in order to catch bugs, and relax them in prod.

I still strongly believe that database constraints are a developer's best friend, in that you can trivially make your data structures fight back against misuse. This makes several classes of bugs obvious. But like anything, there are times they are not optimal.

I'll also say I think there are very few cases where a small performance advantage outweighs the costs, and would be hesitant to head down this path with a team less competent than the folks at Github.
Indeed, greedy and out of touch Hollywood execs are to blame. But as a consumer, we shouldn't really care.
Uhhh Apple is not banning electron. It is banning the use of private APIs.

The only reason Electron is in the news is because it uses some of those APIs.

Now you could argue that private APIs are a stupid idea. But turning this into a conspiracy theory that Apple is on a mission to kill non native apps is a bit far fetched in my opinion.
Ghost wants to retrofit your car so it can drive itself on highways in 2020
I really like go, it's a wonderful language in many ways.

But I really wish we got official answers on things like the code duplication. Either something like generics or code generics and just establish we're not going to get generics and put an end to the discussion.
> I did a deeper dive I learned that tree representations in SQL are a rabbit hole of insanity all arranged around referential integrity.

It’s not crazy, just impractical.

Trees are mostly represented the same way in memory, except you don’t have to access them in table-format, which admittedly for tree-data is very, very cumbersome.
I thought most people like systemd but those who do not are very loud.
> Storing encryption keys or the like in flat text files is surprisingly hard, at least in C.

Storing keys (or other binary) data is _exceptionally_ easy with C. What's hard is _multiplexing_ it with other data in the same file, but you probably don't need to:

some.config:

keyfile=/some/path/to/just/the/key
I wonder how many people would leave the US and give up citizenship. Alternatively this could spur investment into more risk capital as capital preservation might not be a sufficient strategy.
That's not the summary I would have picked. The saved register seems a lot more significant. Shaving off some branches is pretty important too.

tl;dr - bumping downwards saves a register, possibly some predictable branches, and an ADD.
Honestly, "Go tries to be a better BASIC" would be more accurate. Nothing wrong with that, mind you.
I admit I have yet to read TFA but I can answer this quite easily.

We not only tolerate it, we welcome and solicit it with open arms. For the same reason we push industrial waste and exploitative labor to developing countries!
One great thing about not enforcing FKs is that it makes integration testing a lot easier. You can load just the data you need to test with, and none of the FKs need to point to rows that exist that aren't within the testing scope.

This approach isn't for everyone. It works well with DDD where aggregates form contextual table boundaries and is eventually consistent by default.
People age- everyone does it. The industry is going to have to deal with that at some point. Telling old people to leave the industry at a certain point in their career isn't real advice.
Here in Germany they are late about 30% of the time for me but at least that means I get yet another month of free prime.
I think I know the point you are making, but...

They use that number to put political pressure on the DoJ, FBI, and DHS to enforce their IP ownership claims. I get that 100% of their claimed loss would never be 100% of a potential revenue, but AFAIK there is no standard alternative way to calculate those "losses". From what I know, all companies use the same method when describing losses/damages due to hack/cyberattack.
Is Yoga Good for Your Spine?
Electron was simply caught doing something it was not supposed to be doing.

As someone who has spent a lot of time on web and Apple.. this article reads a bit like a conspiracy theory. Apple has allowed a lot of web features on to their platforms and App Store's, like hot code push, PWA, etc.
i will admit that once I saw postgres has arrays and composite types, it seemed more natural to model this as NODE with array of CHILDREN.

I think it's more about the expressivity of pointers and arrays compared to the "backwardness-feeling" of index lookups.
No comment on responsibility or culpability. But, "I want everything for $9 that used to cost $99" is an unreasonable expectation. People paying for cable and satellite are paying way more than the cost of even 5 of these unbundled services. And pay for tv still has commercials. These direct from content producer unbundled apps are still significantly cheaper than the old world. People's expectation of what content should cost seems to be shaped by "I want everything cable does but for the price of netflix." Thats not a delivery volume or price point that ever existed, anywhere.
No app is being booted. New updates are being rejected because of private API usage.

If Electron fixes their usage of private APIs then this whole storm blows over.

Now if Apple introduces a rule that specifically says “non-AppKit apps are not welcome on the store” then let’s panic. But that is not happening here.

(I’ll be the first in line to admit that private APIs and App Store rules are mostly limiting creativity and competition )
If a delivery is late it is often because of how it is packaged, and not purely on the delivery service
Foreign key violations are data corruption!!! It violates the rules of how the data relates and can and will screw up any number of things that depend on the rules being enforced.

Reporting and bi data might get hosed.

Account management might get hosed.

Who knows what happens when FK rules are violated because by definition they should never be violated. It puts all applications on top into a undefined state, leading to bugs and god knows what else.

Foreign key violations are 100% data corruption.
Usenet is still around, and there is content, but for archival purposes, torrents are still a lot more convenient. Years back, publishers started issuing take downs to Usenet provides on specific binary posts. So, as all cat&mouse games go, there were private NZB forums/sites which posted encrypted content and provided the key to members.
The Apple "monopoly" is the biggest driver of progress in consumer computing.

Microsoft only sells adware. Google is spyware (and crapware). Linux tablets don't even exist.

Apple focuses on compatibility, user experience, performance, hardware, ease of use (yet still useful for power users). Sure it's been dropping the ball a bit in the past few years, but it's still lightyears ahead of any competitor.
There's a great video that goes over an old calculator that used delay lines: https://www.youtube.com/watch?v=2BIx2x-Q2fE
So basically they don't use foreign keys because they're into premature optimization.

If you need to shard your database, you're big enough that you'll have the resources to engineer the new solution.

The vast, vast majority of use cases will benefit from the database ensuring the integrity of your data.