I poo on sockets.io
-
Continuing the discussion from Anyone got a good WebSocket tutorial?:
That'll make things easier then. A lot of the devs I work with had never heard of sockets before socket.io >.>
WebSocket's protocol is like 5 lines of code, it could not be simpler. Why the fuck are there bloated open-source libraries for it? Is there anybody left who actually writes code and implements protocols, or is it just bloated, buggy open-source libraries in a huge stack and that's all there is.
I hate this industry.
-
Because it handles graceful fallback in older browsers that don't support sockets so it can emulate the functionality.
But yes, they're all js hipsters who can't code worth shit if you take away their toys.
-
WebSocket's protocol is like 5 lines of code, it could not be simpler.
yes, if websockets are supported by the browser, and if websockets aren't blocked by corp firewall or scumbag ISP.
but given that you can really only rely on ~40% of the internet being able to use websockets you need to code a fallback.
I don't know about you but i'd rather reach for a library that already builds in the fallback which supports browsers all the way back to IE7 era, automatically, and with no change in API to the code i'm writing.
so yes, i reach for signalR/socket.io/whatever ruby gem/some python library to take care of that fallback for me. i don't want to have to get all of that right and maintain it. i want to use someone elses code for that.
But them i'm a little shit of a developer who enjoys coding in javascript on the server side.
-
but given that you can really only rely on ~40% of the internet being able to use websockets you need to code a fallback.
FWIW my use case would be "application running on a corporate intranet".
-
FWIW my use case would be "application running on a corporate intranet".
well if it's intranet only then you probably can get away without the libraries that do fallbacks. you're in a tightly controled environment where you know the browser version and there's no firewall or ISP int he way.
-
-
you're in a tightly controled environment where you think you know the browser version and you think there's no firewall or ISP int the way.
Buttume nothing.
-
......
point.
-
point.
I wouldn't count on a internal corp web app to be used on one browser any more. BYOD, home working, ... but chances are still high that the corporate managed desktop can be used as the lowest bar, most likely IE9.
-
I wouldn't count on a internal corp web app to be used on one browser any more.
You ever seen any home-grown internal apps? The kind that have 400 fields on a screen? You'd have to be pretty dedicated to your phone to try to use something like that on it.
Payroll, ERP, that kind of stuff, would just be awful on a phone. Probably on a tablet, too.
But tbh the big problem is actually more likely to be "we can't use this web version of the product because it requires IE11/Chrome/whatever and we're still on IE8 because of another app we use."
-
You ever seen any home-grown internal apps? The kind that have 400
fieldswindows on ascreenMDI form?*shudders*
-
Well, I was thinking more along the lines of something that looks, to the uninitiated, like that file manager monstrosity that was featured on the old forums many years ago. Sometimes you just have a lot of information to store and don't want 23 tabs in the browser.
-
I have a new thing to poo on.
-
I have a new thing to poo on.
And, like a toddler, you'll regale us with it shortly?
Or did you coincidentally get a new toilet today?
-
I was gonna then I realized it's hard to anonymize and also fuck everybody here lately.
-
-
Is there anybody left who actually writes code and implements protocols, or is it just bloated, buggy open-source libraries in a huge stack and that's all there is.
Because it's boring. Right now I'm writing an HTTP client for Roku because the box gives you a socket and be off with it. It's sooooo boring and there are so many little quirks (caching, headers, etag) that is also very expensive. I wish I had some bloated open-source thing I could throw in there and be done for the day.
-
Be glad it's not HTTP/2 and you can actually read the protocol as a human.
-
Be glad it's not HTTP/2 and you can actually read the protocol as a human.
Overrated. Before the days of text-based protocols, the first step was to write a structure to hold the binary data. Reading the packet data via structure members is trivial.
-
HPACK isn't quite that simple.
-
Oh yeah, that gave us joys like HL7.
And who doesn't LOVE to work on HL7 here in 2015!!!!!
-
HL7.
AFAIK the new version is all XML and enterprisey and shit.
But yeah, I had a brief encounter with it at the uni. 2/10, would not recommend, protocol contained bobcat.
-
-
Is Valve going to pull a
MicrosoftWordPressNetscapeLeisure Suit Larry and skip a few version numbers because they wrote themselves into a corner?