|
Hopefully none of the gawd-awful white ones! 
|
|
|
|
|
Just the normal ones....I do like the coconut ones!
Edit: Just noticed the offensive spelling mistake in the word coconut  now fixed...
modified 20-Dec-13 5:54am.
|
|
|
|
|
I like the gold ones, I like the dark ones. The coconut are just nasty...because they promise chocolate and fail to deliver (which is an evil trick)
|
|
|
|
|
OriginalGriff wrote: which is an evil trick
You're married and yet you seem surprised at getting something other than promised.
speramus in juniperus
|
|
|
|
|
The chocolates I have to pay for.
The wife...
I see what you mean. 
|
|
|
|
|
Have a happy Dave.
|
|
|
|
|
Um.
You missed! 
|
|
|
|
|
Everything that has javascript is buggy, including AJAX and jQuery. 
I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler , half of the stuff has nothing to do with the user it's just there to make it look pretty.
It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world?
Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations.
The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version.
- bragging and ranting over... for now... 
|
|
|
|
|
At some point the development community made the decision to ignore technologies that make sense so that they'd have the time required to embrace steaming piles of horse sh*t.
That is basically how we got our current HTML stack.
It is about assigning oneself importance by being careful to wrap every activity in a very large fog of obscurity and complexity. You'll know who these people are - they're the ones angry that you actually accomplished something.
|
|
|
|
|
Good on 'ya !
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
|
|
|
|
|
OK, now I feel good. Thanks Bill. 
|
|
|
|
|
Part of the reason javascript is unreliable is that 'standards' keep changing. The last two versions of IE (10 and 11) seemed especially prone to breaking older javascript and client-side code. IE 11 doesn't even refer to itself as MSIE 11.0 in the agent string, but instead poses as firefox. (like gecko)
Have you ever tried to browse the web with javascript debugging turned on? If so, probably not for long.
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
It's not the technology; It's the people.
To extend it a bit ... I often say to friends and colleagues:
We may consider our selves as unlucky because we missed the Golden Age of Pericles but for sure we are cursed because we are living the Golden Age of D!ckhead.
It's comforting to know that other people feel it, even if they express it in a totally different way (sometimes like a dogma).
Thanks Dave
|
|
|
|
|
I could give you just as long a list of applications that are desperately in need of offloading some UI to the client. And then again we've all seen the apps where everything is client side and you just beg them to just render it in one go on the server and just give you the info you want.
It's not about the screwdriver. It's about how you hold it while banging in those nails.
|
|
|
|
|
Chris Maunder wrote: It's not about the screwdriver. It's about how you hold it while banging in those nails.
I completely agree until it's a screwdriver and not a hammer. My problem is with the people who use hammer everywhere. 
|
|
|
|
|
A car, nearly completely made of Lego (needed some support)
[^]
In the vid, you can see the individual cylinders providing propulsion...very neat
|
|
|
|
|
My eyes hurt because car's picture looks like pixelated. 
|
|
|
|
|
|
Sorry, seen that too, afterwards. Still, the amount of work that went into that is amazing, never mind the idea that it actually worked/stayed together. I would guess that there is more than a bit of epoxy holding stuff together.
Ken
|
|
|
|
|
What a waste of time 
|
|
|
|
|
Why do you feel it is a waste of time?
It was a waste of time posting your comment....
And least they learned something in the process and produced something tangible to test their engineering capabilities.
|
|
|
|
|
What happen if it hits a human 
|
|
|
|
|
It has a top speed of about 1 mph. If it hits a human it will like stop.
If it hits a human, it was probably the human not paying attention and deserved to be hit!
|
|
|
|
|
محمد م. محمد wrote: What happen if it hits a human
Lego parts everywhere on the street. Suddenly being a bodyman becomes a much more time-consuming job.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
