News for hackers. Stuff that matters.

chrisdotcode

People who are interested in Modular phones can also check out Phoneblok's website[0], which I believe to be the people who started Project Ara.

[0] https://phonebloks.com/

Re:Google seems to have broken email forwarding on Thursday March 05, 2015 @11:32AM (#9151768)
Can you give us more details about your setup, and how you set it up?
There's a common saying that, "Everything about Go is great - except the language".

I guess a book written by Kernighan himself shows how wonderful the ecosystem is.

Re:Jon Ronson: How a Tweet Can Ruin Your Life on Thursday March 05, 2015 @07:51AM (#9150378)
This needs to be the top comment. Can you imagine a person who claims their fight-or-flight response gets triggered by sexual jokes (jokes that were actually more homosexual in content than degrading towards women), but then actually has no empathy for people outside of themselves whatsoever?

People like this deserve no platforms of power whatsoever.

Re:Wiki creator reinvents collaboration, again on Monday March 02, 2015 @05:59PM (#9134961)
You can find the previous discussion about this (from last month) here: https://news.ycombinator.com/item?id=8983158
Re:Ask HN: How to determine legitmate enterprise features? on Tuesday February 24, 2015 @05:21PM (#9103940)
I'm not a religious patio11 reader (as of yet), so I haven't come across much of it.

Good to know he's written more about it.

Re:Ask HN: How to determine legitmate enterprise features? on Tuesday February 24, 2015 @04:53PM (#9103789)
As stated, I wanted to see which features were generic to enterprise in general.

Thank you!

Re:Ask HN: How to determine legitmate enterprise features? on Tuesday February 24, 2015 @04:52PM (#9103782)
Thank you, this helps enormously.

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.

Re:Ask HN: How to determine legitmate enterprise features? on Tuesday February 24, 2015 @04:11PM (#9103548)
I'm going to be selling a B2B SaaS. Rather than be hyper-specific, I'm wondering if there's a list of highest conversion and most wanted enterprise features to sell?

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...

( Read More... | 14 comments | 9 points | on HN )
Re:The New Haskell.org on Sunday February 15, 2015 @06:14AM (#9052337)
http://www.yesodweb.com/book/shakespearean-templates#shakesp...

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.

Re:The New Haskell.org on Sunday February 15, 2015 @05:34AM (#9052279)
This new, awesome site is using the framework Yesod[0], which is kinda like the Rails of the Haskell world, only it can do rad stuff like prevent XSS and 404s at compile time. Yes, you read that right.

[0] http://www.yesodweb.com/

EDIT: To the author, the download and email icons are the same.

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...

Re:The “Web Application” Myth on Monday February 09, 2015 @06:13AM (#9020598)
Word. Blacklist-all-by-default should be the strategy, not haphazard whitelist. Very similar to how you're asked if you want to share your location/microphone/etc with a website - JavaScript should likewise be compartmentalized based on functionality and necessary access permissions should be required of the user on a per-site basis first.
Re:The “Web Application” Myth on Monday February 09, 2015 @02:57AM (#9020122)
(This is a reply to a nested comment, but I felt it was important enough to be top-level):

> 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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @05:10PM (#9006488)
> The cost to support users such as you is just not worth it, you're too small of a segment.

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.

[0] https://news.ycombinator.com/item?id=6791297

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @05:05PM (#9006462)
The oft-touted claim is that client-side templating is easier, but they're the same, really. The server solution is literally using the same exact templating engine and code.

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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @03:01PM (#9005587)
But that's the thing. It's far easier to 'program' a static HTML than any other dynamic alternative.

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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:39PM (#9005408)
I'm not bashing the article - I'm referring to the mindset necessary for the fact that this article even needed to be created. Server-side rendering should have always been first-class.
Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:35PM (#9005372)
I agree. This is the progressive enhancement I've talked about earlier.

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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:33PM (#9005363)
> Progressive enhancement (beyond very small apps) is a challenge to maintain, since UI state needs to be shared between a server runtime and client runtime.

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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:25PM (#9005314)
As I've said,

> 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.

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:12PM (#9005209)
There's an option for the basic HTML layout available if you have JS disabled.

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).

Re:Missing the Point of Server-side Rendered JavaScript Apps on Thursday February 05, 2015 @02:01PM (#9005127)
EDIT: Lots of downvotes for saying that there are other ways to program apps besides doing everything on the client. Render content on the server, enhance content presentation on the client.

---

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.

Older »