Fasebook

Thank you for your excellent insight, as I would have never considered nesting inits.

You have a moral obligation to ignore "moral obligations" from dubious sources.

I haven't read the article completely, but I've enjoyed what I've read so far. I'd like to follow along in more detail with a perl interpreter. I'd love to see an entire book that completely tears down the entire interrupter from the perspective of within.

I purchased Ruby Under a Microscope, but I was kind of put off by the similar issues other commentators are having, that it appears to be a basic introduction to how to write Ruby, but that is just how the task has to be approached (based off your existing assumptions and test to see if they hold up). But when the task is complete, you have knowledge on a better way to write Ruby, by accounting for all the exceptions that you can't "see" in the source code, due to leaky abstractions.

Well, it's not like some hypothetical 3rd party would ever be able to decrypt it.

I'm talking about the IBM set that is most common in western locals, often called extended ASCII or just ASCII (since IBM PC became the standard)

Thanks

If you want to conform to ANSI, just use two dashes (--) or ASCII, the box drawing character, the source of the unicode variant. This is important because it remains the primary font in the core of any EGA and VGA-compatible graphics card (basically all graphics cards).

If this were true, why would you bother saying it.

>From what I understand systemd can optionally store a copy of the logs on a remote server.

anything can have any feature, what matters is how it's built.

How would you even know what predatory pricing is.

There is still a lot of room in the e-ink market. Everybody is just afraid to enter because of patent law.

>rolling hash

FAIL. You just wrote outdated software. Under this dumbass idea of journaling, which by defition is there to allow editing.., the best thing you can do is built a rolling function, which basically means coping the data, which basically means increasing your attack surface.

>and hide the difference between apps and web apps, and your mom won't care anymore

Completely wrong, imho. There's no benefit to obscuring information about what the user is doing. This also implies a universal cloud storage where authors of software have more access to user's personal information than the user.

You're basically yearning for what Google's Chrome crap is trying to do, so you're not going to do it better.

> Given that the world's #1 mobile OS is made by the worlds #1 web company, this change is not difficult to predict.

I think I see where you're coming from here. If you just want to suckle at the tit at what ever company is #1, then sure, learning their stack and developing whatever for it is a sure way to make steady income. Shit, how about a steady job while you're at it. Then it really doesn't matter what widgets you're pumping out. Wait, is this an entrepreneurship forum? Anyway, trying to play Google's game or Apple's game is just a good way to be their bitch. I'm sure you're aware of why "discoverablity" has been removed from appstores. This is a culture war, at some fronts.

If you want to build a digital prison for your mom, go right ahead, but don't expect your kids to embrace this "cloud" stuff in any way that you're dreaming of. You're just building outdated virtual landfill techgarbage the moment you touch any of these paradigms you're talking about.

Linux is not a service oriented architecture. That is really more of an economic model than a viable model for engineering fault tolerant designs.

> This is the old age of power sequencers again. It's coupling.

Is this referring to power transmission or something?

That comment is insane. Why would log files need journaling? They should be serialized.

How is adding a line to a run script "duplicating logic badly"?

Coupling is clearly bad, as evidenced by ... 30+ years of software design, but is a necessary evil. I don't see any reason why it's necessary in such a low level system component. "this is not rocket science" you don't impose dependencies on something you want to be reliable.

Daemontools is clearly the most mature solution, from a perspective of stability. It's probably why nobody wants to use it, there's nothing to play with or exploit for profit because it already works.

What are these "general principles" of "unix philosophy"? Where can I read about them?

edit: thanks, those both look like great books so far.

I can now say Amazon supports IPv6 internally throughout most of the infrastructure.

I'd agree with this premise, but why don't we teach drivers how to build cars?

In other news, YahooLang trends upward on YahooTrends.

Sure, but isn't that the point? I mean, did that stop any of the other gatekeeper models?

This is not the bro culture then. The article confabulates that Silicon Valley culture is "bro culture" and the errors multiply from there. They never establish that bro culture is rooted in Silicon Valley; that is an 'axiom' I haven't heard until this point, but I'm sure if you're from CA, everything comes from CA.

I mean you first heard about this culture in SV right? and most people first heard about it in SV too right? So it came from SV? Wait?

Oh wait, bro culture is just SV culture with frats? Are you sure you're not talking about frat cultures in SV and calling it bro culture?

Next thing I'll hear is how hipsters are all the same and unions are self interested organizations that don't serve their members. Then a tribe will tell me about how evil tribalism is, so I should align my behavior with your tribe's bureaucracy.

Modern businesses that are growing very quickly these days have abstracted away (and outsourced, contrary to the article) accountability. I think that is an important lesson.

It seems to me that there is concerted effort to discredit alternative init implementations.

Example: https://en.wikipedia.org/w/index.php?title=Daemontools&actio...

I can't imagine what agency with a history of undermining technical standards could possibly be involved.

> very few people seem to be able to enjoy it.

Can't imagine why. Oh wait, that's right, people generally work on stuff they feel is sensitive, and they're not apt to go hosting that stuff on some service with insecurity designed in to the foundation.

Is this a joke or did I completely miss the point?

Pretty clear that workers came to SF, worked and then left when they were done. Land value inflation worked as intended.

that's what xargs -n x is for

or "How to make sure only the NSA can circumvent your security"

http is designed for "m2m use case"...