schneems

44 ms·

511.
by schneems 9y ago
There's really good conversation at Lobsters https://lobste.rs/s/oqlrr4/coder_frozen_2009_awakens_find_fr... and Reddit https://www.reddit.com/r/Frontend/comments/6smeff/co
512.
Coder Frozen in 2009 Awakens to Find Front End Development Not Awful(schneems.com)
5 points by schneems 9y ago|1 comments
513.
by schneems 9y ago
Site is down for me. Mirror?
514.
by schneems 9y ago
:) I also think that guilds will be a huge bump with guilds which will allow concurrent Ruby runtimes and allow for passing objects back and forth (currently not available with processes).
515.
by schneems 9y ago
TLDR; no, but it's way faster than you ever would have guessed. Also WEBrick is Ruby's built in webserver if you didn't know.
516.
Is WEBrick Webscale?(schneems.com)
6 points by schneems 9y ago|3 comments
517.
OMG OMSCS: Is an Online Masters Right for You?(schneems.com)
2 points by schneems 9y ago|0 comments
518.
by schneems 9y ago
It depends on how expensive your deprecation process is. I don't think we can generalize for entire ecosystems. Some langs and products it would be fairly trivial to update, and retain back wards compat. Others might be harder and stay
519.
by schneems 9y ago
"Slave" has a meaning in the non-computing world as well and the two concepts diverge. Which is my point. Why is the term "variable" good, it's because it can change, it's variable it describes the concept well
520.
by schneems 9y ago
You're debating the concept of words themselves. Which have meaning. It's the mechanism through which words work. They have both a meaning in context and out of context. They have meaning both intended and unintended. Good technic
521.
by schneems 9y ago
I think there's some low-ish hanging fruit here for Rails to not run validations for fields that were not changed on updates.
522.
How I Reduced My DB Server Load by 80%(schneems.com)
6 points by schneems 9y ago|1 comments
523.
by schneems 9y ago
For most projects it seems like a pretty easy change. You could add new keywords, alias the old methods/commands to them. You don't even have to deprecate them, just make the docs point to the newer terminology. What is easier hav
524.
by schneems 9y ago
I had it in there to emphasize how un-technically incorrect it is. Apparently people saw the word "offensive" and they didn't read the rest, so I took it out to add clarity. I forgot that HN doesn't provide a diff of edi
525.
by schneems 9y ago
> It's not just a replica, it can work offline for a while and push back. Leader/follower is also flawed in my opinion. It's master and a slave even if it offends your sensibilities. I'm glad that your concerned that
526.
by schneems 9y ago
Master/slave was also a commonly accepted role of business for far longer than it has been a computer term. We managed to change that in the west. I believe in us, we can do it. > I genuinely find this argument...disingenuous My arg
527.
by schneems 9y ago
Do you understand the phrase "technical correctness" or is that open to interpretation as well?
528.
by schneems 9y ago
Okay then, be mad that "slave" isn't a technically correct term either. "replica" or "follower" both describe the behavior much better. > it doesn't seem to be a fight worth having Technical correc
529.
by schneems 9y ago
How is changing documentation to more accurately reflect its behavior censorship? Do you think whitespace commits are censorship? Both make for better reading and more accurate representations of our technology.
530.
by schneems 9y ago
"Slave" is technically incorrect. There are better terms to describe the behavior such as "follower" or "replica". If someone has been around long enough to understand what a "slave" is can't fig
531.
by schneems 9y ago
The actual act of slavery existed as an accepted institution for longer than this computing term has. If we can make slavery a thing of the past (in the western world), we can also update to a more technically correct description of the beh
532.
by schneems 9y ago
I think the m/s terminology is not technically correct. The actual behavior of a "slave" would better be described as a "follower" or a "replica". In an IRL master/slave dynamic the master does not fi
533.
by schneems 9y ago
Use threads. They exist. Use em'. Know what threads are really good at? Hiding IO time. They're like REALLY good at it. When a thread is blocked on IO, it's not spinning your CPU. So is the thread "free"? No. Is it
534.
by schneems 9y ago
> What if I have multiple Ruby APIs to hit? Then hit them with multiple concurrent threads and move on.
535.
Using Heroku's Expensive Query Dashboard to Speed Up Your App(blog.heroku.com)
1 points by schneems 9y ago|0 comments
536.
How to write a lock free Queue(schneems.com)
1 points by schneems 9y ago|0 comments
537.
A Tale of Slow Pagination(schneems.com)
1 points by schneems 9y ago|0 comments
538.
Meditations on Writing a Queue(schneems.com)
2 points by schneems 9y ago|0 comments
539.
The Programmer's Guide to Pairing on Pregnancy(schneems.com)
1 points by schneems 9y ago|0 comments
540.
Writers Write(schneems.com)
1 points by schneems 9y ago|0 comments

More ›