chrisdotcode
Sqlite, Google and Phone Calls
I guess a book written by Kernighan himself shows how wonderful the ecosystem is.
People like this deserve no platforms of power whatsoever.
Good to know he's written more about it.
Thank you!
It's this sort of stuff I'm talking about: I've never even heard of an SLA or a support coverage contract (and apparently there are tiers of support?); things that enterprise users want and expect, but that aren't well-known to the common hacker.
If support is common amongst enterprise tiers, I'm sure there are some other things as well.
Ask HN: How to determine legitmate enterprise features?
Besides 'support', I'm not sure what should offer to enterprise users. @patio11 says that I should charge more and have enterprise, but I don't know what big companies want in particular that the basic or premium plans don't cover (or, in truth, what you can get away selling to them).Enterprise features always seem shrouded in a 'contact us' black box, and so there doesn't seem to be a de-facto...
This connection is untrusted
U.S. Marshals to auction off 50,000 Bitcoins forfeited by Silk Road founder
The People’s PRISM
If you're used to only programming in dynamic languages, it can be a shock, but yes, a good type system can do things you never thought possible.
If you were the downvoter, I'll take my vote back now.
This is fantastic. A feature you might not have realized is that it works well with NoScript users. With font-faces considered harmful[0], these icons can be delivered to the user, vulnerability free.
[0] https://hackademix.net/2010/03/24/why-noscript-blocks-web-fo...
Git 2.3 has been released
> and pretending that a site is "broken" if it doesn't work for a handful of geeks is being willfully obtuse.
This is the common rallying cry of the 'use-JS-for-everything' camp. The most important reason a user should have an internet-wide blacklist on JS as the default is because the default should NOT be to allow any website ever to run arbitrary scripts on a user's machine.
That's like always running as root while on a development server. No, wait - that's like having random people from the street have root on your server for arbitrary amounts of time, and all you can do is watch. Principle of least privilege certainly applies to the web as well.
Let's not even mention how an open and private web is hindered by orders of magnitude from Google analytics and Facebook like buttons tracking you across entirely different spectra of websites simply because the sites you're visiting has them embedded.
---
EDIT: Can the downvoters please reply with constructive criticism.
You don't understand. The web is content-based. Like motherfuckingwebsite.com [0] shows, you don't need dynamic content to present your message. If I need to download 1MB of JS to see your freaking tagline, then that's ridiculous.
What people are conflating is "doing things in the client with JavaScript" and "rendering templates in JavaScript", which are two entirely different domains.
You can't access many cool features client-side without JavaScript, full stop. But rendering things on the client, and presenting an absolutely un-usable design without turning-completeness is not content-first design.
What people seem to not understand is that the exact same template that they are using on the client renders exactly the same on the server.
Present a long, full form for JS-less users, and present it all nice-ified for those with, and send it off for server processing when you're done.
It does? Why? The server is handling the data to be rendered either way, and as I say in response to another comment, rendering the data is as simple as:
res.end(render(template, data))
> And your comments about shitty execution of web pages and apps could apply to any shitty app. They have nothing to do with client-side JavaScript applications. I expect a better argument than "I once saw a webpage that sucked".The argument is "you are VC-funded, and taking a 1mil+ dollars to build the Next Big (S|P)aaS. You are spending tons of money on A/B testing, designers, mockups, UI specialists, and your page does not even load for the lowest common denominator - and easiest to manage (static HTML) users of the web?"
The web was built for content-first, not flash.
> The solution is very simple: render all the data on the server, and progressively enhance subsets of your app with JS, by overriding the defaults of the rendered page. It's literally like we're discovering DHTML all over again.
Client.js, rendered on the client:
render(template, data)
Server.js, rendered on the server:
render(template, data)
---
They're exactly the same. You use a templating engine library for either JS, or your server language to process the same data. What client.js should do is change things dynamically, progressively.
That's the second-best approach. The first is using a JS-redirect to the flashy AJAX page, or just overriding all the default handlers necessary with JavaScript (remember, at this point, your content was already (supposed to be) properly rendered for you by the server).
---
I don't get it. Is this 1996? Why are people just now 'discovering' that you don't need to throw JS at an application to have it completely usable?
> All modern websites, even server-rendered ones, need JavaScript. There is just a lot of dynamic stuff you need to do that can only be done in JavaScript.
Really? Look at Linode, Amazon, or even Google (including GMail, and probably others). All of which are big names that can and do work ENTIRELY without JavaScript.
> Client-side JavaScript applications are damn fast.
Another (AJAX) HTTP request + rendering the returned data on a tiny mobile phone is faster than one HTTP request for the entire webpage and having dedicated machinery pre-render the content for you? I don't think so. He does talk about this point later on, but which is it? Client-rendered JS apps are, or aren't fast?
---
JS Hipsters offloading rendering everything to the client for absolutely no reason is the 'everything-looks-like-a-nail' or the 'everyone surfs the web like I surf the web and has my specs' problem. Worst of all, in doing so, they completely neglect actual content. You don't know how many million-dollar VC-funded company webpages I've visited that don't even have a damn tagline visible on their landing page without JavaScript enabled. <h1>s with actual content inside of them are too complicated now?
The solution is very simple: render all the data on the server, and progressively enhance subsets of your app with JS, by overriding the defaults of the rendered page. It's literally like we're discovering DHTML all over again.