skysight-inc/HackerNews huggingface dataset:
Oh certainly. There are a lot of managers that add value. I was talking more about the 5 layers of confusion (product manager, project manager, business manager, business architect, designer) that exist between our customer and the developers. There may be more that I haven’t yet discovered.

We recently spent quite a while on developing a feature only to find out the customer didn’t actually want it.
> It's undeniable that the pace of creation of masterpieces has quickened dramatically at an unprecedented level.

Yes and no. As far as I can tell, the pace of content creation and distribution has been exponentially increasing since at least the Renaissance. So, while it is undeniably true that the current pace is unprecedented, it has also been true at any point in the past you care to examine. This means that the feeling of being overwhelmed by a deluge of new information is something of a constant throughout history.
Personally, I prefer to use each platform for their strengths.

I was looking for a good router which could handle high VPN speeds, while still being usable.
I found for 50 bucks on ebay a "thin client" which sported an AMD cpu with AES hardware acceleration, and a PCIe socket to put an Intel 2xGBit PCIe card I had lying around.
Installed pfSense on it. Works flawlessly. Use few watts (because thin client).

I then found for 50 bucks on ebay a Ubiquiti Unifi AC.

I haven't messed too much with it actually, because I find crazy you need to install a whole Java suite with Mongo and everything to just run the Unifi Controller to be able to configure a bit the Unifi Access Point. I'm considering putting OpenWRT on it. Though I think I will still try this Unifi Controller, because of the advanced guest
capabilities, which is still not as good on OpenWRT.

And then I bought a Ubiquiti Nanostation AC for a Wifi bridge.

For this one, I indeed replaced official firmware with OpenWRT because I can't stand that Ubiquiti makes standard Wifi unusable to push their "Air" technology. I want standards before anything else.

In the past, I "resurrected" cheap TP-Link MR3420 I had for an other project, which were bricked. Amazing that after all those years, I could still reuse hardware thanks to opensource software !

So yes, a BIG thank you to OpenWRT developers ! If any of you are out here, please receive my gratitude =)
I don't think that's really true. It worked well enough, true, but I think it allowed us to not fix deficiencies in a number of areas that we should just have fixed. IOW, I think we survived despite not offering DIO (because other things are good), rather than because of it.
A Tidal Wave of Mud
>I've already had some back and forth with people like you who try to defend the act of evading taxes, and I can warn you: you will never convince me. Let's agree to disagree.

If your debating strategy is to self-proclaim as close-minded and incapable of intelligent conversation, far be it from me to try and stop you :)

And anyways, at some point, if you dig deep enough in people's politics, you always hit the same bedrock: either you're a collectivist and essentially an enemy of individual freedom, or you always give priority to individual freedom before that of the group.

I suspect it's a genetic thing, and you are correct: trying to change one's genetic makeup is pointless via argumentation is basically pointless. Born a sheep, always a sheep.
Newsletters feel like a step (or more like a plunge) back from subscribing to websites via RSS feeds. And yet this seems to be the direction that technology is moving in.

I’ve chosen not to subscribe to certain blogs simply because I don’t want to place my email address in more hands who have no incentive to care about my privacy.
But who will be making the decision to build the next accelerator?
Scientists Have Built “Metallic Wood”
A Framework for First Principles Thinking
Could you expand on why Wine is unimplementable in Wayland?
Situations like these (and others mentioned here) make me nervous to publish to Google Play and are making me reconsider use of their other services namely Google Cloud. A lot of the issues being highlighted here are not simple ToS violations, they have far more to do with psycho automation coupled with an arrogant company culture that is actively dismissive of their customers.
While this can and does suck when it happens to you, this is exactly what it takes to keep products focused so they don't die death by a thousand cuts (or feature requests). For every awesome feature embarked upon, there's an opportunity cost of bug fixes, stability updates, tech debt reductions, and other inglorious but necessary work. Aggressively de-scoping is the difficult but necessary work of keeping a product alive in a competitive marketplace. And yes, it's a marketplace even if the product is open source.
> What edition 2018 has right now is migrate mode NLL which emits an error if either NLL borrowck or AST borrowck think there is an issue with your code.

If that were true, then this example would fail to compile, since it fails with the old AST borrowck: https://play.rust-lang.org/?version=stable&mode=debug&editio...

See: https://rust-lang-nursery.github.io/edition-guide/rust-2018/...
Re: 3

A lot of people keep saying this about X apps but anything written with GTK will be awful because (from what I understand) it’s just paints everything itself and then uses X11 to actually display what it draws. Plus if you run anything over the network like that GLX doesn’t work.

My main two personal complaints with wayland is that writing simple programs without widget libraries is much harder and that the window management is handled by the app (which IMO makes absolutely no sense but maybe there’s something I’m missing, which isn’t crazy since the last time I messed with it was a year or two ago.)

Until those two things get dealt with I’m unwilling to use it.
I'm not saying that, I'm saying a Mustang GT can easily handle 130.

Watch the driving portion of the GT review by Doug DeMuro, he's blown away by the driving experience: https://youtu.be/l5zT005oGbA?t=1123
> Agreeing that there is something worthy of fixing is a first step. It should have happened with this NFS patch and imo some other stuff. The considerations for how and when should be dear with separately.

But there were like multiple people agreeing that it needs to be changed. Including the first two responses that the thread got. And there were legitimate questions around how interrupts need to be handled, about errors ought to be signaled if writes partially succeed and everything. Do you really expect us to integrate patches without thinking about that? And then the author vanished...
A Timeboxed, Day-By-Day #100DaysOfCode Front-End Development Curriculum
Surprisingly slow UPSERT performance
There was a lot of negativity around pipenv a couple months ago.

https://news.ycombinator.com/item?id=18612590

I just use pythons integrated venv and pip, which work fine for me. However, it was in that same thread (the link posted in this comment) which suggested poetry and another I believe, which I do feel like trying out.
The $238M Penthouse Provokes a Fierce Response: Tax It
This is incorrect. NLL is on for Rust 2018 code.

The transition mode is for Rust 2015 code.
> Last week I asked the author of this article to issue a full retraction, because every point is a blatant falsehood.

That doesn't sound reasonable.

> LD_PRELOLAD hacks don't work if the compositor launches the programs - some simple .bashrc trick won't work, and getting the LD_PRELOAD into .bashrc requires being unsandboxed, which itself opens up a wealth of side channel attacks.

This lists quite a few assumptions. Are there many distributions that provide these assumptions out of the box (specifically, the compositor running all applications, and all applications being sandboxed)?

> >4 - A bug in xorg-server will similarly bring down your X session.

A Xorg server needs to implement:

- the display server

A Wayland compositor needs to implement:

- the display server

- the window manager

- the compositor

- the hotkey daemon

- the screenshotting tool

- everything else that is now unimplementable in Wayland, but needs to be in the Wayland compositor because users need them and Wayland compositor implementers have no choice but to provide the features as API extensions.

I'm not really sure what's XWayland's story security-wise, but from my limited understanding, it is a component that is not going away soon, and allows bypassing some limitations of Wayland's API in order to accommodate X11 clients.
> The study you linked talks about saturated fats.

True, saturated fat is probably the worst on this front, and unsaturated fat, if it comes packaged with things like vitamin e (to help prevent oxidation) might not be so bad.

> It's well established that sugars are responsible for type 2 diabetes.

No, it's actually not. This is a popular theory, but it's not very well supported. In terms of NAFLD, a strong contributer to insulin resistance, the worst offenders (in the context of a hyper-caloric diet ) are saturated fat and sugar (at 33% of the effect of sat. fat). Sugar only becomes bad when it's converted to fat, which only happens to a significant degree in hyper-caloric diets, when the liver can't dispose of the glucose quickly enough.

Your anecdotal evidence is nice and all, and may work for you, but is no substitute for meta-analysis of controlled studies.

https://caloriecontrol.org/meta-analysis-of-sugar-and-type-2...
> Network transparency allows you to run an X11 application from any computer on your network and display it on your local computer.

This is a rubbish point. Remote X may work OKish over a wired LAN, but over anything else it sucks. Not even NX uses the X11 protocol any more.

Honestly the only reason people even use it over a LAN is because VNC is so archaic and nobody has written a modern version. Wayland actually makes that easier though.

The point about crashing compositors is good though. Windows can handle a crash in the graphics driver seamlessly. I don't think any Wayland compositors can come close to that.
That's the thing though. The comments at the bottom aren't only racists pedos and trolls, there are also valid opinions that the hive mind has rejected.
It's not just package management. C++ is hugely overcomplicated with features. Understanding C++ is a life project. And the language is unsafe-by-default so you will spend time tracking down segfaults or other UB stuff. Rust allows me to focus on the problem domain, less on the language.
We need a way to unionize across all these properties.

YouTube contributors, Android developers, etc.

Unless we have collective action these companies will simply not care about us.
North QLD flood victims need banks, insurers to be 'good corporate citizens'
Essentially because many Windows APIs are unimplementable in Wayland.

Here is some discussion in Wine's bugtracker:
https://bugs.winehq.org/show_bug.cgi?id=42284
Don't let new jargon and lack of experience with a paradigm influence your notion of self. You are as smart as you were before, and now see the universe just a might bit clearer than before.
Android alone accounted for $31b revenue in 2016, according to Oracle, of which $22b was purportedly profit just for 2016. Excluding Android's contribution to their advertising ecosystem, which is another chunk of that $136 billion you mention. That's far more than 10% of their gross profit, but even if it was less why would that absolve Google of responsibility? The % doesn't create the customer the transactions do.

https://www.bloomberg.com/news/articles/2016-01-21/google-s-...
Our own. I'm a man and virtually everyone here is a man too.
> Wayland is impossible to keylog.

This is an incorrect assessment of the claim which is, "with Wayland it becomes possible to build a system where applications cannot record each-other's events." To the best of my knowledge the only approach with X11 that actually works is running each app with a separate X server. The author points out that being able to register global handlers or programmatically interact with other apps is useful which is why it's possible by asking the compositor nicely. The trick with libinput requires that the system already be pwnd.

Another way of saying the same thing, "you cannot meaningfully sandbox applications that talk to your X server."

> Network Transparency

Is a bad thing and a poor remote desktop solution. Let's say you have a desktop with an Nvidia graphics card and you've installed their drivers. Your laptop is using the OSS Intel drivers. You forward an OpenGL app from your desktop to your laptop -- it will crash. Why? Because Nvidia's libGL expects to talk to a server with Nvidia's GLX extension of the same version.

However, a ton of work is going into getting screencasting and remote desktop working under Wayland in a manner that will let you implement whatever protocol you care to speak on top RDP/VNC.

And VNC currently works on Mutter so I'm not sure why the author is bemoaning it's loss. It's the feature that's getting the most development time right now.

> Multiple clipboards

That's up to the implementor, Wayland had a very general API that's used to exchange data between clients that can be used to implement clipboards in any way the compositor sees fit. Just because GNOME/KDE don't want to maintain it doesn't mean it's not there.

> Restarting ends your session.

If your X server crashes it ends your session too. So this is really an argument that X.org is more stable than Mutter/Kwin. I don't think the devs will argue with that but the point is that they'll get there.
If I remember correctly, heroku has a limit of max 10000 custom domains per app. What are you going to do when you reach that limit, out of curiosity? Thanks
Yea, I think pg_attribute is likely to be the main issue here. For one, it obviously exists many times per table, and there are workloads with a lot of tables. But also importantly it's included in all tuple descriptors, which in turn get created during query execution in a fair number of places. It's currently ~140 bytes, with ~64bytes of that being the column name - just doubling that would increase the overhead noticeably, and we already have plenty of complaints about pg_attribute. I think it'd be fairly useless to just choose another fixed size, we really ought to make it variable length.
>This lists quite a few assumptions. Are there many distributions that provide these assumptions out of the box (specifically, the compositor running all applications, and all applications being sandboxed)?

It's not the Wayland compositor's responsibility to provide an entire security solution, just like it's not the deadbolt manufacturer's responsibility to install an alarm system and security cameras. This isn't a criticism of Wayland, at best it's a criticism of your Linux distro.

Flatpak does answer this question, but fwiw in the Sway camp we're still looking into lighter-weight solutions.

>A Wayland compositor needs to implement: - the display server - the window manager - the compositor - the hotkey daemon - the screenshotting tool - everything else that is now unimplementable in Wayland, but needs to be in the Wayland compositor because users need them and Wayland compositor implementers have no choice but to provide the features as API extensions.

This is only partially true. wlroots implements screenshots the same way that xorg-server does: by providing an API for exporting pixels to clients. The actual screenshot tool is a standalone program which can crash without affecting the compositor. This design is virtually identical to X, except easier to secure. The same can be said of many of your other points.
> Wine is unimplementable in Wayland. By design.

What, why?

> Screenshotting and screen casting tools are unimplementable in Wayland, by design.

They're not implementable without specific privileges or protocols and that is a very good thing. I don't want my calculator app to be able to record eveything on my screen.

> I use the X forwarding feature so often that I have a hotkey on my laptop

This seems like your very specific use case (and wouldn't be impossible in Wayland).
keybase.io with team chat, kbfs and encrypted git repos.
Funny, even after reading everything about privacy and people as the product and whatnot, this might be the thing that gets me to stop using google products
A Brief Introduction to Reinforcement Learning
I read this at lwn.net a while ago but it seems there is no fix to it. How is MySQL doing? I believe Oracle etc are not having this problem as they deal with disk directly.
> Screenshotting and screen casting tools are unimplementable in Wayland, by design

i don't think this is true...i'm pretty sure i've screenshotted desktops before when using GNOME on Wayland.
>Wine is unimplementable in Wayland. By design.

This is false. Wine could be implemented, it would just be less easy than on X11 because it uses relative coordinates for everything. But it's totally possible to convert absolute coords to relative coords and use e.g. wl_subsurface.

>Programs cannot set their own hotkeys in Wayland. You must use the desktop enviromnent's hotkey tool to set global hotkeys.

Yes. This is by design, because it's very easy to turn a global hotkey mechanism into a keylogger mechanism. Also it's not clear how hotkey conflicts should be handled.

Note that there are protocol proposals for global hotkeys.

>Screenshotting and screen casting tools are unimplementable in Wayland, by design.

They already work. See xdg-desktop-portal.

> Some Wayland implementations provide additional features, like screenshotting / hotkey registration, anyway, as API extensions. These extensions are not standardized and require individual support for each Wayland implementation in each program, thus causing further fragmentation.

That's how it works. Wayland doesn't have the magical power to make everybody implement a common interface. For an interface to be implemented, compositor writers and desktop developers have to agree on a design. Drew DeVault said on IRC something that sums up the situation quite well: "Asking wayland for hotkey management is like asking the HTTP standards group for a new HTML element".
Definitely cypress [0]. I can't recommend selenium based solutions if you care about execution speed and don't care about the browser.

[0] https://www.cypress.io/
> > Review in the PostgreSQL community does tend to be on the "harsh" side.

> Can you share an example of a review that you consider harsh? (feel free to share privately, I'm simply interested in what you consider harsh)

I wouldn't use the word harsh, but I do think there's plenty reviews where too much bikeshedding happens.
I would call it a single abusive tweet. Not a coordinated campaign, not specifically targeted at any Twitter user.

This isn't complex.
This is basically the coolest thing ever huge insane thanks for putting this together man, you are a true hero
Do you at least pull whatever is in RECAP?
Rust's ownership/borrowing model is very close to the (often implicit) model of proper pointer handling in a large C codebase. One medium-sized codebase I've worked with tried to be very disciplined about const pointers as a means of passing shared reference vs. ownership, with a style guide about when to use const that strongly preferred const wherever possible. I tried translating the style guide to Rust and found that's it's basically automatic once you add Rust's reference model.

Of course the big distinction is that Rust mandates it. There's lots of C code out there that happens to work fine with shared data structures that never collide in practice (or at least never collide under non-hostile input...) - see for instance every standard libc API that returns a pointer to a static buffer. Our codebase merely had a style guide, and lots of older code was less disciplined. Rust forces you to care up front about everything.
Non Pharmacological Cognitive Enhancers – Current Perspectives (2015)
This also killed many other of things, things we don't even know we're missing. Basically froze the the lower parts of the protocol stack in time.
To get that load off the CPU mostly.
Quantum terrorists could bring down the future internet
Some feed readers offer a private email address that you can subscribe to newsletters with, and see them alongside your other RSS feeds. My reader of choice (Feedbin) does this. It's one way to at least centralize them all in a place outside your email inbox.
Those tools were likely not using Wayland protocol APIs, but extensions specific to the desktop environment you were using.
A lot of the issues would seem to be human behavioural and social stuff rather than the actual information. I mean even before web tech you could in principle learn the vast majority by reading books but most people lack the motivation. And then you think you might just be able to do the exams but a lot of university qualification is just certifying you've been in the vicinity of lecture halls for 3 years or so rather than the actual tests. I'm sure there must be some way to do better.
One complaint in this specific thread is that applications can't control the location of their surfaces (which is needed for things like drop-downs and tool tips), but then again sub-surfaces can be controlled by the parent surface. This specific problem does look solveable.
Did HN just change the “Web” function from Google to DuckDuckGo?
But there are other DBs that could be migrated to, rewriting SQL to another dialect is usually much easier than a full rewrite.
Does it need a whole book to explain? It seems the current post does a fairly good job of getting the point across.
The most glaring deficiency so far is lack of support for the binary NVIDIA driver in most implementations. The whole affair is rather childish.
Thanks for answering.

> The ultimate goal was to become database-independent as far as I understand (I was just a junior dev, this was my first job, so I'm guessing, I wasn't making decisions).

Did you actually achieve that?
Retroshare – “A Secure Decentralized Communication Platform”
From https://en.m.wikipedia.org/wiki/Prescription_costs

“A study has placed the amount spent on drug marketing at 2-19 times that on drug research”
It doesn't work if both ends have NAT.
>- Wine is unimplementable in Wayland. By design.

This is a complicated issue which requires a lot of background to explain and answering it in full beyond my patience.

>- Programs cannot set their own hotkeys in Wayland.

This is a feature, not a bug. Why should clients be responsible for dealing with conflicts between programs that use the same hotkey? What if the user wants to pick a different hotkey? Add keylogging concerns on top of that and the argument for this feature becomes pretty weak. Programs designed with Wayland in mind provide some kind of executable that can be bound to a key in the compositor to interact with their daemon.

>- Screenshotting and screen casting tools are unimplementable in Wayland, by design.

This is a lie, or at least a falsehood born from ignorance.

https://github.com/swaywm/wlroots/blob/master/protocol/wlr-s...

https://github.com/swaywm/wlroots/blob/master/protocol/wlr-e...

>These extensions are not standardized and require individual support for each Wayland implementation in each program, thus causing further fragmentation.

A strong majority of Wayland compositors support these protocols, and talks are underway to improve the standardization process.

>- I use the X forwarding feature so often that I have a hotkey on my laptop to open an Emacs frame running on my desktop (on my laptop's screen). Being able to jump between machines while keeping the entire session, incl. open and unsaved files, is pretty great.

X forwarding still works with Xwayland. Nothing was broken - we have tools for backwards compatability where Wayland is still catching up. Desktops are complicated and it takes a long time and a lot of work to implement them.

But no one is making you switch to Wayland. Keep using Xorg. I doubt you were going to switch anyway, the least you could do is stop spreading FUD.