I hope from the conclusion you can see that my line of thinking shifted this way, but at the time I became so wrapped up in the excitement of it all that I thought I’d hit something!
I have my blog here at the moment https://djhworld.github.io/
It feels a bit crappy pushing to github though, but I worry about the ‘hug of death’ from wanted or unwanted traffic knocking my site offline as all I have are a bunch of raspberry pi’s on my home network.
Might be tempted to join cloudflare with their free account to cache thet content, but that makes me uncomfortanle too!
If you decide to use Cloudflare, you might be interested in this: https://lobste.rs/s/czdb39/dear_customers_cloudflare_appeal
I don’t use many of the “native” OSX applications either, with Calendar being the exception. It’s not that bad, seems to function well. My only concern right now is with each OS upgrade, the OS appears to be using more and more RAM. You need at least 8GB of RAM to run OSX these days, 4GB just isn’t enough.
I wouldn’t move to something like Linux, even though I secretly would like to, but I’m too invested in the OSX ecosystem. I’ve purchased and regularly use applications like: -
etc. These are great and some of them are not cross platform. Admittedly a few of them are designed to correct or improve features in OSX (e.g. Alfred) but I find I’m using them every day.
I think the issue he is having with the hiring process is with his line of questioning
Taking in stdin, doing some transformations and then putting the result to stdout is easy in most languages, but in Java it’s a pain as there are so many different ways to do it, e.g.
BufferedReader bi = new BufferedReader(new InputStreamReader(System.in));
String line;
while ((line = bi.readLine()) != null) {
....
…etc. I have trouble remembering that snippet and often have to search my snippet library for it if I ever need to use it in my code.
Plus, combined with the fact that most typical Java developers don’t tend to write command line applications, with a lot of application development focused around the web/server side of things, you can kind of understand why this might present a problem to Java developers who’ve never ventured outside of their IDE.
Great observation. I’ve always avoided “use a library” questions, but hadn’t considered reading stdin might itself be such a question.
I think this is a good idea, I often find myself frustrated at man pages for not providing decent examples. While I enjoy the depths man pages often go into, sometimes an example usage section is all you really want.
Also I think the community maintenance and “wisdom of the crowds” approach of the “bropages” is a nice touch too.
The only slight irritant for me is the dependency on Ruby, the start up time to spin up the runtime is grating, especially when compared to opening man pages is almost instantaneous
I like the speed of it. It seems much easier to me most of the time to see a few quick examples of common use-cases than to wade through a man page listing every single option and what it does, with no examples until 20 pages in.
Honestly, I think that this is a bug and the Chrome team is just being lazy about it.
If the
typewasn’t provided, I’d expect this behavior, but Chrome shouldn’t be allowing you to embed the wrong type w/ the same URL that the right type was hosted on before. That’s the issue here in my opinion.The chromium devs have commented on their bug now, as the spec bug has been raised they’re probably going to look at fixing it once the spec has been finalised.
In both Firefox and Chrome they handle it differently, Safari seems to be the only one (from what I’ve tested, I didn’t test Edge or Opera!) that is very opinionated.
Well that’s good news :)
I would assume Safari is more strict w embed anyway? I hope so anyway