Supermighty

The scar on the face of Paris.

Usually it's just an interviewer's gut feeling. I don't believe there is a formal set of criteria that is used as a filter.

You paint a picture of Apple ignoring all QA responsibility and pushing it on the users, only to later ignore their requests. Surely this is not the case. It's just another bug that slipped through. It doesn't have to be the result of a greedy corporation cutting corners.

I completely agree. No one sets out to create bugs in their software. I'd give the engineers working on this the benefit of the doubt versus a grand conspiracy of product apathy.

I agree, I think the PHP community wants this to be successful, and is looking with rosy thoughts. But I find it hard to blame them. PHP paid my salary for a long time. It's got a few issues as a technology, but it gets the job done. I can see how the PHP community would look forward with hope.

I watched a video too that was celebrating the downfall of the counterfeiter, and it mentioned there was something on the bricks, like a film or a grease. I can't imagine that is healthy.

And only if Windows would stop spying on me would I give this more than a passing glance.

How can I be expected to trust a computer/OS that I can't fully configure.

The price is nice, but what is the lifetime compared to something costlier. A S10+ cost almost twice as long, but if it lasts twice as long then it's a wash.

Though, Google still wins when it comes to updates. Even given that project treble would make the process easier, I doubt that Samsung will really take advantage of it.

I wouldn't say that I need GPU to render my terminal, but if the alternative is to just let the GPU sit there, unused unloved, then I'll take the terminal that accelerates using the GPU.

I'm glad to see plastic make a return. I don't mind the metal, but I couldn't buy a glass backed phone. I remember when the Nexus 4 came out, people everywhere had broken glass backs.

Alacritty uses the gpu for acceleration, where iTerm uses it only sometimes. That might have changed in a recent release, but originally iTerm was limited in when it used the gpu.

I notices it a little bit when moving around quickly in NeoVim.

I use iTerm. There are alternatives that are faster, like Alacritty, but iTerm has a ton of features. It's hard to beat.

I understand them wanting to discontinue browsers that have very low usage and have discontinued support from Microsoft, but I can't help but feel a little sad about the narrowing browser engine ecosystem.

The only reason Google tried the nanotrenching is because AT&T fought them tooth and nail on using the telephone polls.

Calling Kong _just a wrapper_ is dismissive of the features and value it brings to just a web server. Kong is an ecosystem in it's own right, with a plugin development kit and an open source community supporting creation of an intelligent proxy.

When would I want to use DB-less ? Isn't that where the configuration lives.

What would be the best way to deploy this with my application in Kubernetes?

Minification, fingerprinting (md5 tagging), and similar features are being worked on for Hugo, and should be avail soon: https://twitter.com/GoHugoIO/status/1009923838346514433

For speed alone, I wonder how Gitea would compare to Gitlab.

Gitea is written in Go. I used it for a small self hosted instance; it's fast for me, but I wonder if it scales well.

I was taking photos of locations I visited. Google Explorer's program offered free 100GB of Google Drive space once you reached a certain level. About a month after I started they changed the promotion and took away the Drive space. So I deleted all my photos and stopped taking new ones.

Never work for free.

It's so fast. More websites should strip down their size to favor speed.

Well said.

Rob Pike is explicit about early Go development; everything that went into Go was agreed upon by Robert, Ken, and Rob. If all three didn't agree it didn't go in.

There is a difference between magic and automation. Magic is about obfuscation, hiding, and keeping the programmers only using the surface tools.

You can auto-generated code as long as the programmers know the what and why for.

They go through the spiel every time I get an oil change. Always show me a near clean air filter and tell me it's time to change it.

I wonder if a side effect--or conspiratorially the intended consequence--will be a culling of older, poorly implemented poorly supported, plugins.

It is really important to keep a journal. It is even more important to review and reflect using your journal.

I think disabling the arrow keys is a mistake for someone just coming to vim. The arrow keys can act as a warm blanket of familiarity while learning the harsh winter of vim. When a noob is making mistakes and getting frustrated having the arrow keys work like normal is a comforting reprieve.

Once someone has a couple of months of vim under their belt then would I recommend disabling the arrow keys.

I've always used mywebsite.localhost

> since if they start with a brand new root certificate then I'm not sure what happens with the older browsers.

IdenTrust will cross-sign Let's Encrypt root cert. I imagine they will keep it cross-signed, for backwards compatibility, once LE has their root cert in all the browsers.

Sid is always unstable. They'll create a new branch for Testing.