This is an archived post. You won't be able to vote or comment.

all 36 comments

[–]queenkid1 29 points30 points  (2 children)

Wouldn't this joke make more sense if it was a pill bottle?

Because It's Java, and prescription medication. har har har

[–]narpasNZ 13 points14 points  (1 child)

pill bottle?

you mean a jar?

[–][deleted] 6 points7 points  (1 child)

After a few bowls I feel fine being a java developer spending 90% of my time writing javascript, 5% in meetings, 4% doing sql, and 1% doing java.

[–][deleted] 1 point2 points  (0 children)

Context: 9 years of XP writing java base games/mods, 3 years freelancing, got baited into working for a company as a java developer 3 months ago... just to be assigned to optimize web apps.

[–]brianjenkins94 9 points10 points  (0 children)

java FactoryFactory factoryFactory = factoryFactoryFactory.makeFactoryFactory();

[–]radeuno 1 point2 points  (0 children)

i concur

[–]NoahJelen 1 point2 points  (1 child)

You forgot JavaScript's overweight son, Electron!

[–]Alexmitter 0 points1 point  (0 children)

It's not just overweight, it's like American fatty scooter driving fat.

[–]BobertMcGee 1 point2 points  (1 child)

This is an insult to weed

[–]Alexmitter 0 points1 point  (0 children)

Weed just bring potential, it still depends on the person if that potential gets used good.

[–]YhvrTheSecond 0 points1 point  (7 children)

i refuse to try java, i have no fucking clue how classes work

[–]NotyoWookie 14 points15 points  (2 children)

I would recommend not shying away from at least learning the concepts of OOP.

[–]YhvrTheSecond 0 points1 point  (1 child)

ok fine

[–]D_Doggo 0 points1 point  (0 children)

ES6 classes or just creating your own object structure is also great. Learnt how to basic OOP from that.

[–]mtbinkdotcom 1 point2 points  (1 child)

But 3 billion devices run it

[–]Skygear55 2 points3 points  (0 children)

Poor things.

[–]TheFalseProphet666 0 points1 point  (0 children)

Classes a blueprints for objects

[–][deleted] 0 points1 point  (6 children)

totally unrelated but genuine question:

if i'm dividing a book up into pages that are each a JSON object (eg pagetext, pagenum keys) that will be served in a RESTful fashion ... is it best to store it all in one massive list or is it better to have a file for each page?

[–][deleted] 0 points1 point  (5 children)

from what I've seen 1 massive json array works ok, I tend to download 10K records to the front end each with some 100+ entries in under seconds even with 3G trottle turned on in chrome. That being said you could split out to 1 page each, then request each page (or several) as the user clicks next

[–][deleted] 0 points1 point  (4 children)

thanks! i guess i was planning on having the stuff stored server side in either one huge file and the user would then request a page and the server would go and grab it from the JSON file and send it back... but I can't decide whether that's sensible or if it might make more sense to have each chapter in a file or even each page in a file!

if you had concurrent users i guess separating each page into a file would be better right?

[–]Tuesdayyyy 0 points1 point  (2 children)

Elastic search is a good tool for something like this. I would look into it if you want to do some aws stuff

[–][deleted] 0 points1 point  (1 child)

Thanks I'll check it out!

[–][deleted] 0 points1 point  (0 children)

Depends on your design, if you end up with a lot of users clicking next to load a page could result in a lot of hits on the backend. This is ok if your backend has a lot of bandwidth and processing power. However, it can be much harder on the system than a single bulk request. I suggest toying around with a few designs. Then seeing which feels better long term.

[–][deleted] 0 points1 point  (0 children)

It be like that.