How does this relate to media sites? eg. Netflix, HBOGo, the rest of the cable channel web apps? If a user clicks on a thumbnail preview and is taken to a separate page with a video, will they now need to click on it to begin playback? Or is clicking on the thumbnail an "expression of interest" that can somehow be tracked across pages? For Netflix, how does this impact autoplaying the next episode of a show?
If the above UX issues can't be solved for, this is a hammer which is going to have an adverse impact on a growing part of the web.
I'd be interested to know what (aside from the new wasm support) the PSPDFKit standalone web viewer offers over PDFJS. We're currently using the latter, which is good enough for our needs, stable and actively developed, and open source. It does a lot of the work via Web Workers, and on desktop at least, it's performant enough for viewing even unusually large PDFs full of raster images.
"evergreen" means self-updating, with a rapid release cycle. Chrome, Edge, and Firefox follow this model. IE (essentially a legacy browser at this point) and Safari don't.
Interesting stuff out of this thread.. I really love Soundcloud, especially for discovery, but I guess I'm an absolute edge case. I primarily listen to electronic DJ sets (RA, Dekmantel, etc) and the community track ID comments on these are great for discovering new music. I rarely even look at the feed.
yeah, ridiculous student loans (med school), and some of it is definitely unrelated to being in the bay - a lot of debt related to the substandard paid maternity/paternity leave when having a kid in the USA (shoulda got that job @ netflix in retrospect...).
but kid-related costs here are also out of control, accredited infant daycare is insane, and you pretty much have to take what you can get into. same with after school care. this alone is >$3k/mo.
CA self-employment tax is nothing to sneeze at either, especially if you're a contractor in an industry that makes having an s-corp unfeasible.
My wife and I work full time, combined income is just below $400k. With a mortgage on a 3 bedroom in Oakland, daycare and after-school care costs, student loans, et al, we have never been more broke in our lives. I was living large when I was making $75k and not living in the Bay Area... now, it's beans and rice most nights, and hoping the early 2000's honda doesn't break down on the way to school.
Anyone remember LOD (Land of Devastation)? It never gained much traction but was an awesome idea at the time with it's downloadable tile packs. Unfortunately the really shitty gambling system made it godmode all around.
omfg! i was on many Dementia BBS' in SoCal back in the day. First board I sysop'ed was a WWiV 3.21 - I was very proud that I modded the Pascal source to support more than 9 discussion boards at the time.
i know this is a tangent and not directly related to next.js, but the react ecosystem's insistence on coming up with increasingly convoluted and self-defeating stories around how to handle CSS instead of just using the tool the way it's intended is pure insanity. the emphasis with styled-jsx favors encapsulation with no real thought put into external overrides or customization, which makes this a non-starter for creating vendor components that are actually usable. compare https://github.com/zeit/styled-jsx, which can only euphemistically be called a naive implementation, with the documentation around custom properties, with the styling documentation at https://developers.google.com/web/fundamentals/getting-start....
This is really cool, and very nicely packaged. I agree with some other commenters that showing sample html would be a good improvement, but in general this is awesome.
That said...
Is it acceptable to animate `box-shadow` these days? Thought that was a pure framerate killer on mobile.
i think the killer feature of gitlab is still self-hosted instances. it makes it really hard to justify using github enterprise. as far as gitlab.com, i've toyed around with it on personal projects and it still has a very long way to go in terms of reliability and speed.
Whatever gains Mr. Robot made in "killing" (i'd say updating, but anyway) the Hollywood "hacker" trope, they lost twice over with their shoddy portrayal of mental illness.
Hi Paul, why not address the real issue in the FAQ? As it stands now, using React in a project essentially nullifies any patent protections a company may have against Facebook. If I were to use React to build a successful product that fits into Facebook's business plan, there is nothing I could do to prevent them from stealing my concept wholesale.
they may not have been necessary for your projects, but they're absolutely necessary for any real-world production grade apps. Angular is solely targeted in that direction. 90% of the React examples I see when I interview people are handlebars/mustache 2016, and would be better solved with server-side rendering in the first place.
Ah, Microsoft. Will they ever figure out that the Microsoft name is a liability for consumer app adoption? There's a reason it's not called "Facebook Instagram", and Facebook, deservedly or not, still has a much less tarnished image than MS.
Please elucidate? Angular 1.5 has one-way binding, lifecycle hooks, component tree architectures. UI-router is well on the way to become framework agnostic. Redux or redux-style state management is possible with ng1.5, and a pleasure with ng2.
On top of all of that, you get the benefit of using a framework instead of patched together libraries. Basic tools like intercepting all http traffic at the request/response level is incredibly helpful with larger apps.
The only differentiating factor really left is JSX, and while that may be a personal preference, angular style templating is a lot more comfortable for developers used to server-side templating (JSP, Razor, et al)
Came here to say this. Recently spent a day hand-rolling my own, much like the author here has, only to rip it out at the end of the day and replace it with a lightweight wrapper around IntersectionObserver, using the polyfill. The API is just great, really well-thought out and much better than what I had come up with. The only downside is that I'd gone to some pain to get everything working with RAF, and the polyfill doesn't bother with that.
"Over 90% of the time that prototype turns out to be good enough, either because the problem is abandoned or remains at a level where a rewrite isn't worth it."
You might want to spend some introspection time on that statement.
Came here to recommend Stormpath, too. I don't actually use their API but the docs are amazing and some of their presentations on REST API design are phenomenal.
The world, and Silicon Valley startup culture in particular, is filled to the brim with oblivious narcissists. You can pry my nagging self-doubt from my cold, dead fingers, thank you very much.