throwaway77384

Also discussed here I think: https://news.ycombinator.com/item?id=22348251

This is ridiculous. I have never even heard of NeoTokyo, but this soundtrack just blows me away. Thanks, man. I love stumbling upon completely random recommendations like this.

Complete speculation: They make their money by assessing back-links. So they crawl as many websites as possible, as often as possible, to establish some kind of view of who is linking to what. From that, they extrapolate some kind of popularity score, which they can probably correlate with keywords and types of users and searches.

That is what they sell back to users, presumably. I am actually quite interested to see how clear their data / recommendations would be, but haven't had the time to do so yet.

I can heartily recommend you something called Dokku, which more or less takes all the pain out of Docker. I had no experience with this, but got fed up of spiraling Heroku costs. Decided to slap Dokku on a €2.50 pcm VPS, runs like a charm. Multiple containers all communicating with one another, staging, production, failover environments, shared storage, all behind multiple SSL-secured domains.

Dokku is single-server only, however. So if you need a Docker swarm, you'll have to do that yourself :)

Hey, glad to see you are monitoring this. I certainly tried this already (and even got as far as your support team stating they would be happy to do this for me and then somehow it never happened and I was instead sent down a long rabbit hole of different people and phone calls. I'd love to send you some feedback on this if you are happy for me to send you an e-mail?) Thanks

Still kind of confused about the seemingly arbitrary 30 sites limit for workers sites. If I am a professional web-developer, I am going to need to deploy a heck of a lot more sites than 30. There is no option to get access to more than 30 sites other than signing up again and again with a new account (and the same payment details? Will that even work?) and paying a number of different $5 monthly invoices. A really unnecessary hassle. It would be much nicer if this limit was either lifted, or it became possible to increase the number of sites. I felt the whole point of workers sites is ease of deployment, which is nice for a single blog, but really only becomes powerful when one is cranking out multiple websites monthly.

Anyone here have experience with workers sites as part of a similar business model as mine?

I always appreciated the raw performance of nnn.

Every action is ridiculously instant, even over remote ssh sessions.

Kudos for making a truly fundamental tool :)

not the same, as it isn't free :)

No worries. I wish I was able to give better feedback, but I am nowhere near as expert a user as many others surely are.

I like how 'on the ball' you are with this though, it's that kind of passion that makes projects like nnn so strong!

At the risk of embarrassing myself: The ":s" verb for easily viewing the size of directories / files, the overview of multiple directories at once, the gitignore handling, at a glance. There might be more, but I would have to spend more time with it.

disclaimer: my definition of "devops" is sitting in a remote terminal for where I run docker and chasing down which files take up all my precious space, or not remembering where I put something, which makes the tree overview very useful. I know I could achieve this via many other means also (and did before Broot), but Broot is also very pretty, so I quite like that, too :)

You know, I hadn't considered that. This distinguishes nnn from Broot. I would revise my comment if I could, but in the absence of that ability, consider this my correction.

I second this. This has replaced nnn for me and solves so many devops headaches. Excellent work!

This should teach anyone that tackling something that's considered "the basics" is not a bad idea. It is astounding how these really simple things can still be enhanced (or even revolutionised ;)) in 2020.

I second this, please, oh lord, tell us!

Just wanted to chime in and say kudos for speaking up. That sure is a risky thing to do. Unless, of course, this is just more smoke and mirrors.

I like to believe it is not.

I moved away from all Google services (which I used to be keen to get involved with initially! How times have changed.) over the last few years. I don't miss any of them.

There are alternatives for everything. While you're at it, do the same for Facebook, Instagram and Whatsapp, if you can. I only have Instagram left.

Could this get around a locked bootloader on a Sony Xperia Z5 Compact? (As in, the normal sony-website-enabled bootloader unlock NOT allowed when checking in service menu)

If so, there might be a bounty out for it...

Presumably microLED will be the holy grail. When I first heard of OLED it was another 20 years or so before it started to really show up. So, I'd expect microLED to be making waves in 2030-2040 lol

I'm running LOS 17, which is Android 10 on a Sony XPeria Z3 Compact (!!) without issues (though it requires open g apps nano for GPS to work) :)

Couldn't agree more.

I have only ever run into dealing with InfoSys' services (back in 2011 or so they provided the entire media / marketing / advertising tech stack for Diageo, called Neo at the time).

Complete black-box. Impossible to work with. Impossible to get documentation. We literally had to debug via crash reports delivered to us every 24h. Of course it was ALWAYS their machine images somehow differing from their environments, so our tests passed locally and then failed in their black box.

Horrific performance problems (think services locking up at 200 concurrent connections...for mobile apps, when advertising-apps were still a thing. Released across virtually all pubs in a whole country. You can imagine how that went).

Of course they would continuously blame all their issues on the company I worked for at the time. And Diageo even fought tooth and nail to defend them. We had to waste an insane amount of resources just proving to them that their system sucked. Easily one of the worst examples of a company wasting huge amounts of money, thinking that outsourcing would save them money. It's so stupid.

Quite fascinating, but a bit short and low on details.

Hug of death, anyone? :)

Hug of death.

Archive link: https://web.archive.org/web/20190921030912/http://esr.ibibli...

Glad to see Go Template make the list of languages with the most curse words in them.

NOT Go, but Go Template!! A subset of Go is causing more anguish than all of Python and only a sliver less than all of Rust.

Says it all really ;)

Still waiting for them to respond about a month later. Chased up multiple times. Nothing.

They won't keep me as a customer much longer.

I think, and don't quote me here, Optane is still an order of magnitude away from RAM in terms of IOPS (read latency). It's massively better than traditional SSDs, but RAM is still waaayyyyy better. So, Optane could be useful as boot drive and fast-ish swap space, but that's probably it. In most applications Optane won't feel that different from your usual nvme discs. I think. I can't afford one, haha

You make a very interesting point. As a reasonably recent dev (three years ish), starting with Python (and Kivy), then Go, then HTML/CSS/JS, I can see some consistent patterns emerge.

I've built a few apps with frontends by now and every, single, time, I could not tell you whether my frontend code is any good.

In Python I sort of know when my code is good. It 'feels' good. It might not be clever or amazing, but I can get it to a point where it doesn't repeat loads, is reasonably easy to read even months later and behaves consistently and can be tested easily.

In Go I feel this effect even more strongly. It feels quite wholesome to me.

Frontend? ¯\_(ツ)_/¯

I just can't get to a point where I am satisfied with how it's setup. Yes, I can make it work, but it never stops feeling messy. I don't want to use a billion libraries or frameworks either. I like to do my own thing (having tried some frameworks, I felt I was mostly working against the framework).

Javascript-anything always feels yanky. No matter how much I optimise it to death using webworkers, try every CSS trick in the book to load things as quickly as possible. On my 4.5Ghz 4790k with 32GB of ram, everything I do always hitches, stutters, jitters and doesn't feel smooth. This is true for the web (and that's after adblocking). Like, how is that the state of things? Browsing the internet on a weak work-machine without adblockers is literally unbearable. I simply don't do it.

So I don't know what this predicament is we find ourselves in nowadays, or whether I need to spend more time with frontend work, but overall it feels far messier, far more difficult to get right than the backend stuff I have built. Anyone have any pointers as to how one deals with FE work?

Even simple sites quickly turn into a mess of thousands of DOM elements and every time I try to write non-repeating code, I notice one more setting or attribute I need to switch particularly, so then I am adding yet another conditional to a function or writing another function, which basically does the same thing, but not really...

Wish I could go backend-only, lol...

  That statement needs to be challenged. 
  The Montessori method might be great at small scale in an educational context, but that doesn't mean it's a great way to run a company worth most of a trillion dollars. 
  Yes, empowering employees is good. Yes, having a few "coddled geniuses" to drive basic science or radical innovation is good too. 
  OTOH, having every single engineer haring off in random directions all the time might not be so great.

Your whole post seems to be very reasonable, but there is one thing I'd like to mention, which is that you will immediately run into problems if you have rigid standards for what constitutes a "genius" and who is part of the just "the normal engineers". A "genius" can't very easily be defined. Historical examples like Mozart or Einstein make it easy to think that there are only a few geniuses whose talent is immediately entirely obvious to everyone, and the rest of society is merely average.

That is not true. To bring that kind of potential about in many people who thought they were not geniuses prior to encountering an environment where their skills are fostered is one of the greatest advantages a company could possibly have.

Some might just call this "good HR", or "caring about people". I have worked in companies where there were people who truly cared about their employees and about their strengths (and who could not afford the obvious "geniuses") and who thus almost "created" these geniuses. I know there are many ways in which I am simplifying this and I know that no company should try to employ purely geniuses. I have worked in a small team of six "very, very advanced" people in their respective fields. It was basically impossible to create any kind of cohesion. I would suspect it would be similar with other teams of "geniuses". Maybe not, but I think you are overall right in what you say, but it is so incredibly important to understand that the lines between a "genius" and a "run of the mill" developer may be more blurred than most people expect.

I think I was mainly trying to avoid risking that anyone reads this and thinks past performance is an indication of future performance.

Your point is perfectly valid and is a useful addition to my prior post.

I understand that back-testing is a foolish way to work out whether a bot works, but it'd be interesting to see how this performs on arbitrary lengths of past history. Like, is this enough to beat a lazy index fund calculated over the same time, with interest reinvested?