Honestly I don't know why people keep throwing money (fiat, lol) at bitcoin projects.
82 karma · joined November 21, 2014
Honestly I don't know why people keep throwing money (fiat, lol) at bitcoin projects.
It's interesting how these racist ideas get tossed about proudly here and in the US media.
It's really tiring to see bitcoin promoted as some sort of second-coming-of-Christ when all evidence points to it being nothing more than an interesting experiment.
> Just bribe a leader and you're home free
Heh, far from it. See this documentary about Chinese operations in the Congo, for example:
https://www.youtube.com/watch?v=A0C4_88ub_M
Getting anything done in Africa is a pain in the ass, and it goes far beyond just bribing the right people.
Haha! Counterexample: practically every programmer in my country.
None of our cities are "software tech hubs" like you'll find in the USA, UK or Germany.
Your other comments already make you sound like a petulant child and a moron (or at the very least, someone with no actual real-world experience), but this just the cherry on the cake.
SQL is extremely powerful, and using it effectively doesn't take much more effort than learning another new mainstream programming language.
Anyway, enjoy your tortured use of shitty ORMs + Mongo for your toy projects; move aside and let the real programmers go on with their work.
I can't remember the last time I stood in line at the supermarket for an hour because VISA was clogged with "dust" transactions. Hmm.
Take the lighting network for example. The idea has been floating around for quite some time but in practice its still vaporware.
Yet, ask any bitcoin enthusiast what's being done to solve the scalability problem and the LN is trotted out as if it were already widely adopted. It's ridiculous.
There is a complete lack of acknowledgement of bitcoin's ineptitude as a replacement for current payment methods, what with its 2TX/s limit (on a good day) and the ridiculous size of the block-chain which effectively negates all the advantages of it being a distributed system since you have to rely on third-parties to use it on you phone or embedded devices for example. Not to mention the monopoly that chinese miners have on the network...it's a joke.
IMHO bitcoin is an interesting experiment, but that's all it is. It will be replaced by something better some day, another fact that evangelists refuse to concede.
It is $CURRENT_YEAR, yes.
> Software engineers are still obsessed with squeezing every last drop of performance from a single core, adding multicore or distributed load support as an afterthought.
Normally I'd agree, but if you had bothered reading the abstract the performance losses were not negligible and the kernel scheduler was responsible for the losses. This has nothing to do with application programmers not understanding "distributed programming" as you put it.
From the article:
> As a central part of resource management, the OS thread scheduler must maintain the following, simple, invariant: make sure that ready threads are scheduled on available cores.
> As simple as it may seem, we found that this invariant is often broken in Linux. Cores may stay idle for seconds while ready threads are waiting in runqueues.
> In our experiments, these performance bugs caused many-fold performance degradation for synchronization-heavy scientific applications, 13% higher latency for kernel make, and a 14-23% decrease in TPC-H throughput for a widely used commercial database.
While technically true, you're ignoring a ton of other factors such as the lack of any other alternative employment or the lack of financial capability to move to an area where more employment exists.
When the only jobs available are McJobs, then that is what you are compelled to do, to support yourself and your family - regardless of your intelligence or qualifications because someone else is ready to take your place if you don't accept the job. You have no power to negotiate a higher salary regardless of whether or not you deserve it.
It is a very hard rut to pull yourself out of and stay free from. Companies like Walmart exploit this as much as they can, and have no reason to change their behaviour unless forced to do so.
> I never contacted Facebook or Alex using my work email account. It was only after Alex contacted my employer via email that I sent a reply from my work account. Alex indirectly contacted me at work, not the other way around.
> I never contacted Facebook or Alex using my work email account. It was only after Alex contacted my employer via email that I sent a reply from my work account. Alex indirectly contacted me at work, not the other way around.
Also, why would he be doing this work at the behest of his employer when (IIRC) Facebook's bounty program only pays out to individuals? It would automatically make him ineligible to claim the bounty.
To me it seems like Alex Stamos tried to use some good old threaten-your-livelihood intimidation tactics and failed miserably.
If that post made you feel this way, then her follow-up article will have you cringing and wincing:
http://sarah.thesharps.us/2015/10/06/what-makes-a-good-commu...
Aparently she knows for a fact that all those points definitely make a good community, despite never having run one the size and scale of the Linux kernel project.
Pure arrogance and entitlement.
> Quoting Linus: "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'Git'".
>('git' is British slang for "pig headed, think they are always correct, argumentative").
https://git.wiki.kernel.org/index.php/Git_FAQ#Why_the_.27Git...
Haha! You can't really be serious!
For example, yesterday I burned ~750kcal on the treadmill. Are you trying to tell me this makes no dent in the calories I consumed throughout the day?
If my objective was to lose weight, are you implying that doing such a workout couldn't lead to a calorie deficit and therefore expenditure of stored fat?
Rust seems to be a saner alternative, but isn't production ready.
Hello me, from a parallel universe!
You've basically described the project I'm currently assigned to and the situation I'm in as well, and I share your enthusiasm for "weeding" out obvious turds and warts from the codebase.
Unfortunately I've reached a new kind of roadblock when it comes to improving and refactoring the project: I've picked all the low-hanging fruit, and now if I tug at any of the remaining lose ends the whole thing will unravel.
Basically the remaining pain points are architectural ones (that will hurt us at scale) and that require attention but at the same time are large enough that management won't approve the necessary resources to work on them.
Honestly I almost feel as if I've fucked myself over by making those improvements: the project is now mediocre as a whole, but just good enough so that nobody really cares about improvements any more. Had I just let the ship sink, maybe something better would have come out of this whole mess in the end.
Not sure what the lesson here really is! :|