Is ruby dying?
-
Look guys can we just slag off ruby instead of a political discussion :)
-
@antiquarian said in Is ruby dying?:
In favor where appropriate (everywhere except dessert).
-
@lucas1 said in Is ruby dying?:
Look guys can we just slag off ruby instead of a political discussion
You seem to imply that comparing programming languages is not a political topic.
-
@cartman82 said in Is ruby dying?:
Nah. Once they close the last .NET shop around and kick you to the curb, you'll need all the money you can get for reeducation courses into javascript developer foot masseurs.
No need. SQL is still widely used after 40+ years, and there are always tons of whiny front-end developers who are unable to wrap their heads around it. Why waste $20k on a 35-week Javascript bootcamp bootcamp bootcamp?
-
@Groaner said in Is ruby dying?:
@cartman82 said in Is ruby dying?:
Nah. Once they close the last .NET shop around and kick you to the curb, you'll need all the money you can get for reeducation courses into javascript developer foot masseurs.
No need. SQL is still widely used after 40+ years, and there are always tons of whiny front-end developers who are unable to wrap their heads around it. Why waste $20k on a 35-week Javascript bootcamp bootcamp bootcamp?
Isn't that why things like MongoDB have been built? To avoid SQL? I mean, that's why they call them NoSQL databases after all. So see, no problem in moving on towards @cartman82's NodeJStopia!
-
@Dreikin does Poe's law apply here?
-
-
@Dreikin said in Is ruby dying?:
@Groaner said in Is ruby dying?:
@cartman82 said in Is ruby dying?:
Nah. Once they close the last .NET shop around and kick you to the curb, you'll need all the money you can get for reeducation courses into javascript developer foot masseurs.
No need. SQL is still widely used after 40+ years, and there are always tons of whiny front-end developers who are unable to wrap their heads around it. Why waste $20k on a 35-week Javascript bootcamp bootcamp bootcamp?
Isn't that why things like MongoDB have been built? To avoid SQL? I mean, that's why they call them NoSQL databases after all. So see, no problem in moving on towards @cartman82's NodeJStopia!
My understanding was that the square wheel of NoSQL has backpedaled into "Not Only SQL," so that developers have choices for storing unstructured data to complement their relational databases, provided there exists someone with such a use case.
-
@Groaner most SQL databases offer a Json type now as well. But I have no idea why you would want to use it.
-
@Groaner said in Is ruby dying?:
@Dreikin said in Is ruby dying?:
@Groaner said in Is ruby dying?:
@cartman82 said in Is ruby dying?:
Nah. Once they close the last .NET shop around and kick you to the curb, you'll need all the money you can get for reeducation courses into javascript developer foot masseurs.
No need. SQL is still widely used after 40+ years, and there are always tons of whiny front-end developers who are unable to wrap their heads around it. Why waste $20k on a 35-week Javascript bootcamp bootcamp bootcamp?
Isn't that why things like MongoDB have been built? To avoid SQL? I mean, that's why they call them NoSQL databases after all. So see, no problem in moving on towards @cartman82's NodeJStopia!
My understanding was that the square wheel of NoSQL has backpedaled into "Not Only SQL," so that developers have choices for storing unstructured data to complement their relational databases, provided there exists someone with such a use case.
Sort of. There exist plenty of people who are happy to re-invent relationships for NoSQL databases using application code.
-
@Maciejasjmj If you were doing it the OOP way you would pass IShape.
Edit: Ignore me I am being an idiot.
-
@Dreikin they avoid SQL because 'joins are slow' and such shit like that.
-
@Arantor It is a similar sort of logic where you call people racist when you don't agree with them.
-
@Arantor said in Is ruby dying?:
@Dreikin they avoid SQL because 'joins are slow' and such shit like that.
Right, because
@Groaner said in Is ruby dying?:
there are always tons of [...] developers who are unable to wrap their heads around it.
no?
(which is not to say there are no legit reasons to use a NoSQL db. But these aren't the ones we're talking about, so )
-
@Dreikin said in Is ruby dying?:
@Maciejasjmj said in Is ruby dying?:
They're trying to push it cross-platform, which to me is not the greatest idea, but just like you, Microsoft seems to have drunk the hipster Kool-Aid.
Any hints of a declarative cross-platform GUI toolkit/framework in the recent .Net moves?
They apparently decided to settle on Xamarin.Forms, which is currently supported on Windows 10 and OSX (...plus iOS, Android, and Windows 10 Phone).
I wouldn't be surprised to see versions of it for Linux, but who knows which widgets it will use on that.
-
@powerlord Technically, being on Android, there's already a Linux version
-
@RaceProUK said in Is ruby dying?:
@powerlord Technically, being on Android, there's already a Linux version
I'm too lazy to look up what the current XWindows servers are, so...
-
@powerlord GTK# , it installs the fucking toolkit on My Mac and my PC when you install MonoDevelop, and I know that shit is on Linux.
-
@antiquarian said in Is ruby dying?:
Besides, if it did happen, most of the stuff we see now on the front page (at least those of us who still bother with the front page) wouldn't compile and therefore wouldn't be submitted. Where would we be then?
hahahahahahahahahahahaha
you are underestimating the wtf. it'll live, no matter the language
-
@Jarry said in Is ruby dying?:
you are underestimating the wtf. it'll live, no matter the language
Never Underestimate the Power of the WTF!
-
@lucas1 said in Is ruby dying?:
@Groaner most SQL databases offer a Json type now as well. But I have no idea why you would want to use it.
Persistent events. There's often a lot of variation between events, and not much you really care about querying.
Choices are basically: a table per event type, a big events table with a TYPE column with many nullable columns, or a big events table with a TYPE column and a serialized blob of all the event-specific fields.For example, lets say I had a CLIENT table, and wanted to store all events which cause a change in a CLIENT_EVENT table.
Using a JSON column, it could look something like:Event ID Timestamp Client ID Type Event Data 5 2016-11-02 09:24 4 Created { firstName: "William", lastName: "Doyle", birthDate: "1970-03-05", emailAddress: "william@example.com" } 21 2016-11-03 14:32 4 BirthdateAmended { birthDate: "1970-05-03", reason: "Was written in month/day/year format instead of day/month/year" } 37 2016-11-04 12:44 4 NameChanged { firstName: "Bill", lastName: "Doyle" } 429 2016-12-04 13:21 4 Deleted { reason: "Bludgeoned to death with an avocado :(" } I could have these as separate tables for each type, but I don't really see a benefit to it and the effort to maintain them would grow larger as more event types get added. Similarly, I could have a single CLIENT_EVENT table with many columns, but it wouldn't really be clear which columns are used in which event types.
-
@Groaner said in Is ruby dying?:
My understanding was that the square wheel of NoSQL has backpedaled into "Not Only SQL," so that developers have choices for storing unstructured data to complement their relational databases, provided there exists someone with such a use case.
So XML or JSON types in SQL Server?
-
@Jaloopa Hasn't SQL Server's XML type been around longer than the NoSQL craze?
-
@RaceProUK probably. The only new things in NoSQL are objectively worse than what already existed
-
@kt_ said in Is ruby dying?:
Also, there's always PHP.
Explore previously untouched opportunities, such as the development of mobile apps, games or IoT apps in PHP.
Yeah, make the world even worse why don't you.
-
@aliceif said in Is ruby dying?:
@kt_ said in Is ruby dying?:
Also, there's always PHP.
Explore previously untouched opportunities, such as the development of mobile apps, games or IoT apps in PHP.
Yeah, make the world even worse why don't you.
Karl Marx said it best:
PHP is the sigh of the oppressed creature, the heart of a heartless world, and the soul of soulless conditions. It is the opium of the people.
-
@kt_ Marx was a cunt.
-
@Salamander No this makes a lot of sense
-
@lucas1 said in Is ruby dying?:
@kt_ Marx was a cunt.
And you're a fucking moron.
Wanna discuss Nietzsche again? Dickhead?
-
@lucas1 said in Is ruby dying?:
@kt_ Marx was a cunt.
Which one? I hear Groucho could get a bit nasty but Harpo, Chico, Zeppo and Gummo were lovely guys
-
-
@lucas1 said in Is ruby dying?:
Marx was a cunt.
-
What ISN'T dying then?
-
-
-
-
@lucas1 said in Is ruby dying?:
@kt_ said in Is ruby dying?:
And you're a fucking moron.
That had the intended effect.
The effect of you confirming you're a moron?
-
@Ascendant I think it might be better to ask a Buddhist that question
-
The
effectaffect of you confirming you're a moron?FTFY
EDIT: I am not actually sure now. Since it is a strange sentence.
-
@lucas1 said in Is ruby dying?:
The
effectaffect of you confirming you're a moron?FTFY
EDIT: I am not actually sure now. Since it is a strange sentence.
"effect" is right.
-
@Dreikin said in Is ruby dying?:
@lucas1 said in Is ruby dying?:
The
effectaffect of you confirming you're a moron?FTFY
EDIT: I am not actually sure now. Since it is a strange sentence.
"effect" is right.
I don't generally care that @lucas1 has problems with spelling and grammar. However whenever he tries to correct others, it does bother me.
-
@lucas1 said in Is ruby dying?:
I am not actually sure now. Since
it is a strange sentenceI am a proudly ignorant little windbag without a clue.FTFY
-
@flabdablet Weev al had enuf ov lisning at "expurts"
-
@Jaloopa said in Is ruby dying?:
@Groaner said in Is ruby dying?:
My understanding was that the square wheel of NoSQL has backpedaled into "Not Only SQL," so that developers have choices for storing unstructured data to complement their relational databases, provided there exists someone with such a use case.
So XML or JSON types in SQL Server?
Well, yes, if you want to be boring and sane and oh-so-2007*.
*Yes, I'm aware that JSON support is a more recent addition to SQL Server.
-
@Salamander said in Is ruby dying?:
Persistent events.
Or structured logging in general. You probably don't want a separate table for each of your log messages, but it might be nice to have some key-value pairs atrached to them - AOP method logging, for example, can serialize the method parameters into JSON and store it this way.
Azure's Application Insights kinda works like this - among other bells and whistles such as timing info, most message types have property bags you can filter on. If you want to simulate it in a database, JSON is probably your best bet.
-
https://what.thedailywtf.com/post/954835
How the world changes
-
@Arantor said in Is ruby dying?:
NodeJS has maybe a year before something new and cool comes along and steals its thunder
This is apparently not the case yet, two years on. I has a sad
-
Meh, I have come to like node over the time. With the new webpack and React its actually a pretty decent stack. And, as of now, IE < 11 is dying more with every day, so... it's getting there.
I however long for the day when the JS api stabilizes...
-
@bb36e as a programming language?
-
@pie_flavor correct, bb36e-as-a-programming-language is my monetization strategy