romaniv

29 ms·

271.
by romaniv 9y ago
>Manually handling the DOM is probably the biggest cause of spaghetti code. This isn't true. The biggest cause of spaghetti code in "traditional" JS is due to having multiple conflicting sources of truth for the same pie
272.
by romaniv 10y ago
In the good old days of ICQ and Jabber you could install a client that would integrate several protocols into a single lightweight UI (e.g. Miranda IM). Unfortunately the new wave of messengers is much more successful at guarding their prot
273.
by romaniv 10y ago
Trying to replace paper with eInk isn't wise. However, those devices could have other, entirely new usages. For example, digital blackboard that consumes little power and can be remotely updated would be extremely useful. This isn&#x27
274.
by romaniv 10y ago
I'd buy one in a flash. Color is overrated, while the ability to work in sunlight and display an image when computer is turned off / sleeping would enable me to do things completely impossible before. Also, it would be cool if suc
275.
by romaniv 10y ago
You probably should watch that video. This is one of its core subject. Kay makes a valuable distinction between invention and innovation, and what you describe falls into the "innovation" bucket. It's incremental. Yes, our ce
276.
by romaniv 10y ago
There were many advances in chemistry, medicine and biology, materials and manufacturing, but not all of them translated into something that's truly transformative as far as society as a whole is concerned.
277.
by romaniv 10y ago
Alan Kay spoke about it length in many of his talks. For example: https://www.youtube.com/watch?v=gTAghAJcO1o Excellent video. I highly recommend everyone working in or with IT to see it. I think he is right. PCs and smartp
278.
by romaniv 10y ago
>The value proposition is "You can use the same code on both the server and client" With differences in standard libraries, environment specifics and even language features available, I think a far more accurate statement wou
279.
by romaniv 10y ago
I've been thinking and reading about OOP and its roots recently. Here are some interesting resources on the subject: Alan Kay's elaboration on what he envisioned when he coined the term: http://userpage.fu-berlin.de&#x2
280.
by romaniv 10y ago
It's a chicken and egg problem. To get a lot of incoming links you need to be popular. To become popular (via search engines, at least) you need a lot of incoming links. This heavily penalizes smaller websites and rewards incumbent pla
281.
by romaniv 10y ago
Related anecdote. I used to write for an amateur online magazine with product reviews and analysis of a certain industry. It wasn't big, but the content was good - not just in my opinion, I was told that many times by various readers.
282.
by romaniv 10y ago
I'm not sure why anyone is using scrolling events for any standard websites at all. It's much easier to have a function on timer that detects the current viewport position and acts accordingly. The code is simpler, the performance
283.
by romaniv 10y ago
CDN-hosted scripts, for starters. Also, running old games in DOS Box is often a finicky process that requires some tinkering for every game. That's one of the reasons GOG.com took off so rapidly. People are gladly paying several bucks
284.
by romaniv 10y ago
Fixed it.
285.
by romaniv 10y ago
A demo of sorts: http://quickenloans.github.io/Behaviors.js/ The code will look extremely non-idiomatic to most frontend engineers. Treat it as a thought experiment (which it is). The important thing isn't the par
286.
by romaniv 10y ago
Couple years ago I gave some thought about how to handle reusable JS in a sane fashion. Actually, a lot of thought. The end result was something that superficially sounds like Web Components, but it quite different underneath. I guess a goo
287.
by romaniv 10y ago
Those are pretty handy features, but they are not nearly enough. I know plenty of people who spend several hours a day entering, validating and fixing data in giant Excel spreadsheets because they need to work with multiple systems that don
288.
by romaniv 10y ago
We can't automate filling out Excel spreadsheets, but investing 4 million dollars in automating music creation. Meanwhile there are plenty of CC-licensed tracks and plenty of aspiring composers/producers who would gladly work on c
289.
by romaniv 10y ago
Anything that requires human approval for routine operations quickly devolves into bureaucracy that adds a lot of manual steps without any real safety. Now, you may argue definition of "routine operation", but the thing in the art
290.
by romaniv 10y ago
Some website being Slashdotted is not in the same class of issues as users' (possibly encrypted) page content being spread all over the web. Also, the notion that you either need to use some super-centralized platform or be susceptible
291.
by romaniv 10y ago
> I think the whole benefit of a static website generator in general is to avoid the "I copy/paste the same header/footer on each" step, especially copy-pasting the menu/header, as your menu can change as you ad
292.
by romaniv 10y ago
Search is more than Google. There are many other search engines. And I'm not just talking just about Bing. I'm talking about the likes of Yandex and Baidu with huge user bases. Do you know whether they can crawl SPAs? What about A
293.
by romaniv 10y ago
This is a classic. Definitely worth watching for everyone working within IT.
294.
by romaniv 10y ago
>If a website doesn't have at least minimal functionality, then the website is broken. Curious. This goes completely against the sentiment in all of the discussions around modern SPA frameworks and JS libraries I've seen on
295.
by romaniv 10y ago
I edited the post because I thought someone will nitpick on my comment about hardware, but it seems you caught the older version. > This is a fallacy, AlphaGo didn't increase very much with additional hardware at all It did. Pleas
296.
by romaniv 10y ago
>And let's take a look at AlphaGo, how would you do that with SVMs or decision trees? This is a poor example. There are Go programs that work very well and use exclusively MCTS without any neural networks.
297.
by romaniv 10y ago
>I'm not sure I fully buy the "explainability" argument against deep learning since our goal is human level intelligence and human intelligence isn't easily explained either. There are two types of explainability. O
298.
by romaniv 10y ago
The grandparent post contains a hint of something I've already heard in lectures and from ML practicioners: boosting and random forests are more resilient to improper tuning (to put it another way, they are more universal and work well
299.
by romaniv 10y ago
XSL was not envisioned as a middle layer between HTML and CSS. Plus, it was a quintessential design by committee, trying to cater to a bunch of conflicting use cases with no overall vision or conceptual elegance.
300.
by romaniv 10y ago
IMO, HTML/CSS have always been missing a middle layer. It really should be: - HTML for pure information - Something else (template/view?) for layout and (possibly) forms - CSS for styling in terms of fonts, colors, etc. This would

More ›