cfv

18 ms·

151.
by cfv 10y ago
I don't like this; their general MO has always been google giveth, and google can take it away. Introducing inconsistency can only lead to more people trying to disagree post-facto with google, and eventual lawsuits
152.
by cfv 10y ago
Hi! Author here! I made a thing! Declarative HTML requires, where requiring practically anything is a data attribute away. In its current incarnation, all it does is load HTML and put its components in places that make sense, replacing the
153.
Show HN: HTML requires(cfv1984.github.io)
2 points by cfv 10y ago|1 comments
154.
by cfv 10y ago
More red states have a death penalty than blue states; also, none of the perpetrators of these https://en.m.wikipedia.org/wiki/Lynching_in_the_United_State... could be characterized as a leftie
155.
by cfv 10y ago
Neat. Now, why not actual CSS?
156.
by cfv 11y ago
This can be beautiful, but I'd need SOME KIND of back-compatible functionality, even if it's just to tell old IE users "hey you're totally missing on stuff, check this out"
157.
by cfv 11y ago
How exactly would performance degrade by defining a virtual machine for C programs to run in where assurances are given that all of the standard behavior is fully defined -this operation either fails, or gives THIS result-? It sounds like i
158.
by cfv 11y ago
You can always distribute a "full" package like many popular products do, with all the dependencies lodged in place. It's a damn convenient thing to have at dev time, but there's 0 need to enforce build processes in PHP
159.
by cfv 11y ago
You can always do a local deployment, zip the thing, and rsync it anywhere. It's not at all a necessity, it's just that most PHP devs have embraced Composer. In fact we used to do something rather similar at my job, until we just
160.
by cfv 11y ago
Kinda. What this people are talking about are actually extending the DOM with actual nodes that are programmatically defined. You could never do this kind of stuff to the DOM with XML+XSLT
161.
by cfv 14y ago
Pot, meet kettle?