Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lewisjoe
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
41 ms
·
421.
▲
by
lewisjoe
7y ago
This is where differential synchronization shines (basically git). While OT/CRDT are really good for syncing small edits, they suck at being eventually consistent (with intentions preserved) on very large edits. We make a powerful coll
422.
▲
by
lewisjoe
7y ago
If all the clutter of an word-processor on the screen, is what bothers you - there's Zoho Writer ( https://writer.zoho.com ) that could help you. The online word-processor provides contextual options without as much clutter a
423.
▲
by
lewisjoe
8y ago
We are building Zoho Writer, a full featured word processor for the browser ( https://www.zoho.com/writer/zia.html ), and we use NLP (Deep Learning) for suggesting grammar corrections & writing tips to users.
424.
▲
by
lewisjoe
8y ago
Honestly, CRDTs are quite complicated to understand. No amount of blog posts, research papers or diagrams will truly click (for most). And like somebody else said in comments, most articles on CRDTs assumes the audience are math people. I&#
425.
▲
by
lewisjoe
8y ago
I worked at a startup and then switched to a bigger product company: Zoho. If there's one thing I'd take away for the rest of my career from Zoho, it would be frugality in adopting the latest of tech. When NoSQL was all the rage,
426.
▲
by
lewisjoe
8y ago
Thanks. I'll try to make a spreadsheet out of this when I find time. I've got quite a few non programmers who'd benefit from something like this.
427.
▲
by
lewisjoe
8y ago
Anybody out there using J2V8( https://github.com/eclipsesource/J2V8 ) for such purposes?
428.
▲
by
lewisjoe
8y ago
When it comes to creative freedom vs reusable blocks, the latter will always win. Period. Assembly language provided creative ways to solve a problem. C won because it had patterns to solve them across projects. Word processors provide crea
429.
▲
by
lewisjoe
8y ago
Clear, crisp guide. Thanks a lot. > Those that ask things a lot and can't do much, assign them small tasks. This is what I'm stuck with. Most times when this happens, I blame myself for not being capable of empowering them. Lik
430.
▲
by
lewisjoe
8y ago
> I think the big deciding factor for me was that it handled rich pasting better than all other platforms. I can copy from my editor (IntelliJ) and paste into it and the format is preserved perfectly. I guess you are looking for a fully
431.
▲
by
lewisjoe
8y ago
I've briefly analysed ProseMirror as well as Quill. IMO ProseMirror seemed well built with better literature compared to Quill. ProseMirror's author has truly thought out every API and has got most of the details just right. For e
432.
▲
by
lewisjoe
8y ago
ProseMirror is easily the best source code I've ever worked with. The components are so well architected, that inside the codebase there's a 100 page book on software design principles waiting to come out. I'm serious. Marijn
433.
▲
by
lewisjoe
8y ago
Here's an interesting observation from recent HN reactions to JS: + The hardcore server folks are hating JS these days, because it requires more than dropping a single script tag. + The full-stack people / JS beginners are hating
434.
▲
by
lewisjoe
8y ago
Django(Python) for backend. React for the front-end. Pros: + You are already a bit familiar with Python + Django provides out of the box solutions for authentication, db management, migrations + bunch of stuff that takes quite a bit of effo
435.
▲
by
lewisjoe
8y ago
Rails (or Python or Java) doesn't really fit into the problem set that JS has to go through. Most softwares written in those tech stay in the server with no need of transpiling, no need of code splitting when built, no need to be sent
436.
▲
by
lewisjoe
8y ago
There's nothing wrong with handwritten scripts. The lack of problems are exactly why the current dev workflow has scaled and I'm saying this as of 2019, which I find interesting! The problem is opportunity cost. The rest of the
437.
▲
by
lewisjoe
8y ago
Well, for those of us from the 2000s era of web dev ES5 wasn't such a deal breaker. It isn't very concise, but ES5 isn't so bad either. ES5 to ES6 isn't what Java is to Python. It's more like what Python 2 is to Py
438.
▲
by
lewisjoe
8y ago
The problem though was Webpack was generating massive bundles (probably something to do with the polyfills needed for different browsers). We were able to achieve much smaller bundles by just sticking to ES5 features supported by the browse
439.
▲
by
lewisjoe
8y ago
I just wrote a proposal for my team today as to how the front-end tooling has changed recently and why we'd need to adopt them in our workflow. https://writer.zoho.com/writer/open/0y4wx08838bdbcf954b1398c...
440.
▲
Ask HN: Anybody still into ES5 + traditional Javascript dev workflow? Why?
3 points
by
lewisjoe
8y ago
|
2 comments
441.
▲
Code and Data Are the Same Thing (2011)
(wiki.c2.com)
1 points
by
lewisjoe
8y ago
|
0 comments
442.
▲
Show HN: Writango – Make Presentable Notes and Blogs
(writango.com)
3 points
by
lewisjoe
8y ago
|
0 comments
443.
▲
Show HN: Writango – Write Blog & Publish As Presentation
(writango.com)
5 points
by
lewisjoe
8y ago
|
0 comments
444.
▲
What Svelte Really Is
(gist.github.com)
2 points
by
lewisjoe
8y ago
|
0 comments
445.
▲
by
lewisjoe
8y ago
This is true. I wasn't much tech savvy back then. I switched to Chrome because it made my internet fast. Of course it might not really have, but the sleek look, the circular loader instead of a progress bar kind of a loader that Firefo
446.
▲
by
lewisjoe
8y ago
Thank you!
447.
▲
by
lewisjoe
8y ago
I agree. I may have misinterpreted the original comment. Yes, in that way XML is indeed a better way to put it. I'd still stand by my opinion on not-making formatting information as separate tags and blowing the tree one level deeper.
448.
▲
by
lewisjoe
8y ago
Sorry, it came off that way. Yes, HTML is not XML. I meant any XML-ish representation of rich-text contents. Which means every formatting block makes the tree grow one level deeper.
449.
▲
by
lewisjoe
8y ago
This category of standards for structured text will look simple and sufficient. But they break once you bring in more complicated formatting options like font-size, background colour, etc. Which is why we need rich-text standards that aren&
450.
▲
by
lewisjoe
8y ago
> XML is superior to JSON for text documents. Far superior. Why do you think so? Is it because most structured texts are Trees? If so I understand the appeal. Because hey, HTML is perfect isn't it? Except, it's really not. Whil
More ›