Live data from Hacker News

Fine, I'll build my own text editor

dbushell.com

261–264 of 264 posts

Re: Fine, I'll build my own text editor

#261
post #249

Earlier quoted context omitted.

> Sounding and being are not the same thing. I'm familiar with his stated opinions regarding both generics, and syntax highlighting. They check both the "sounding" and "being" boxes quite nicely.

Dude has worked on UTF-8, Plan 9, and a very popular language despite its flaws. I am not accomplished enough to judge him. Nor have I had the pleasure to meet him in person to pass any judgement. I don’t get this obsession with tone policing, probably borne of corporate tendency towards blandness and inoffensiveness. The vast majority of interesting people are eccentric and with their unfiled corners, it’s part and…

> I don’t get this obsession with tone policing,

That's weird, considering I was saying he was wrong about something. That's not tone policing? The breathless hero worship in your comment is ironically a much more insidious form of tone policing.

> The vast majority of interesting people are eccentric and with their unfiled corners, it’s part and parcel of being outstanding in your field.

When you grow up, you'll (hopefully) learn that "being loudly and confidently wrong a lot" and "being unpleasant to work with" are not in fact correlated with any particular metrics of technical success, nor are they part of being an "interesting person". Quite the opposite in fact! (Although TBF it does correlate pretty well with certain measures of "success" and longevity in business and large organizations.)

I don't actually know very much about Rob Pike, but the two issues I've heard his opinions on, they were both wrong and poorly argued. I appreciate you don't think I should be able to say this, but I don't think your tone policing is appropriate for this web site.

Re: Fine, I'll build my own text editor

#262

Yes, who would have guessed that the element, designed specifically for this use case and built into browsers for 3 decades, would be the most performant and behaviorally consistent way to implement editable text. I'm kind of sad the author stopped shedding unneeded complexity there though... we're not really building a text editor yet, we're building a website with a fancy input field. If we want to build a proper t…

So we take a web browser and trim it down to only ever show a single element you say? That's what I'm taking away from this. All the hard work for accessibility is already done then right?

> So we take a web browser and trim it down to only ever show a single element you say?

I was saying if the goal is "text editor," the web platform is the wrong foundation entirely

Re: Fine, I'll build my own text editor

#263

Earlier quoted context omitted.

He created Go because he believed that the average Google programmer is too stupid to program in C++, and he didn't like Java, the other language created to address this problem.

> He created Go because he believed that the average Google programmer is too stupid to program in C++, and he didn't like Java, the other language created to address this problem. It is more nuanced than that. Created Go because: a) C++ deemed excessively and unnecessarily complex, overloaded with features, increasingly difficult to manage b) Very slow compilation times c) Wanted a language with built-in concurrency…

its too bad they basically gave up the core of the idea and added generics. in a terrible way none the less
Post reply on HN