Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "oranges"
-
>Wife texts me to buy her 10 oranges on the way home from work
>Arrive home with 2 oranges thanks to working with binary..
Believe it or not this actually happened after I had just finished a whole binary-related project over the span of around a month.6 -
Windows vs Linux vs MacOS, Android vs iOS,
PHP vs .Net vs Java vs python vs whatever,
Angular vs React vs Elm vs vanilla ...
It's like Nintendo vs Sega,
Star Wars vs Star Trek,
Beatles vs Rolling Stones ...
It's all a bit childish, right?5 -
Just had an interview with our new potential product manager. I companioned our CEO, if technical questions arise...
First, he came to our office, to the interview, and never..never looked at our application. Neither he saw some screenshots, review's or anything related to the product. As a potential product manager...gasp
And he really tried to impress me, by mentioning what a great full stack developer he also is (LOL), with years of experience in frontend and backend.
But, since I am an android software developer, he mentioned he don't like java. But he loves java script...
Me: ehhh what? So you compare apples to oranges. Why do you don't like java? (And I could image a lot things ...)
Him: because unlike JavaScript, java is a mess when writing code.
Me: ok Iam done.9 -
There are 3 incorrectly labeled fruit baskets (all 3 are incorrectly labeled). One basket has only ORANGES, another one has only APPLES, and the other has mixed ORANGES-APPLES. You can't see anything. You can only pull out 1 fruit from 1 of those baskets. With that, move each label to it's corresponding basket.2
-
Legit Apple Interview
There are three boxes, one contains only apples, one contains only oranges, and one contains both apples and oranges. The boxes have been incorrectly labeled such that no label identifies the actual contents of the box it labels. Opening just one box, and without looking in the box, you take out one piece of fruit. By looking at the fruit, how can you immediately label all of the boxes correctly?
Those who got it answer it directly on Saturday/Sunday until then good luck10 -
anyone else ever focused so hard/long that they peeled an orange(mandarin) to eat, then forgot to eat it so long that it was crispy?
i mean like literally the thin skin remaining was actually crispy... this is me taking a break to remember last times i ate/etc... and hopefully not have more crispy oranges... though tbh wasnt bad10 -
if (!rant) Fuck oranges
else
It's about time we make some God fucking damn things fucking God fucking clear. What the fuck does programming have to do with fucking non-programming?
Honestly. Fucking fucks pretending to be fucking programmers (probably not you, but fuck off if you're one of those fuckers.) FUCK SUCH PEOPLE FUCK YOU FUCK FUCK fuck FUCK!
There. Now that's out there. Leave fucking programming to the fucking fuckers who fucking know some-fucking-thing fucking ab-fucking-out it. If you're learning, ask questions, without you there'd be no fucking future for good fucking programmers. But if you're a fucking fuck fucking ducks in the fucking park--fuck the God fucking damn the fuck OFF!3 -
A tech as well as a life question (actually more of a useless sleepless thought) : What do you think is more important? Exposing yourself to multiple technologies, career paths and life experiences or diving deep into a single technology, career path and life experience?
I feel like being an expert in 1 tech might pay off in terms of job life , and it would be bad for a person who is constantly switching between career paths, but sometimes i feel like i should have tried other paths too. Not just the life of a techie, like people who are deep into media and journalism, accountancy or those film industry jobs ; politics or finances , etc.
Its like, we found an apple to be a tasty fruit and now we have to be the apple guy forever. The better i am in being the apple guy, the more i will have to eat apples and the more i will earn. Why can't i try pears or oranges?7 -
It drives me nuts when people compare iPhones to Samsung, not realizing that Samsung did not invent Android, nor are they the only phone manufacturer or Android OS distributor.
If you're comparing iOS to Android, that's one thing. Or if you are comparing iPhone's hardware to a specific Samsung phone's hardware, I get it. Heck, I'm cool if you compare the iPhone X to the Samsung Galaxy Note 8, because they're similar in price. But don't say that Apple is better than Samsung when you mean you have an issue with Android, or your battery life on your $300 Android device wasn't as good as your $700 iPhone. Apples to oranges guys! It's like comparing Visual Studio 2015 to Python.
I don't care who is right or which is better. At least know what you're comparing!
Thanks.2 -
Ok I'm going to jump in on the new iPhone shit, yes they are expensive, yes they are pale in comparison to flagship android devices (no I'm not an apple fan at all but I like Mac) but you don't buy an iPhone for the hardware, you buy it for the software and custom silicon.
iPhones will probably out perform android in synthetic tests for ever, they are working with custom designed hardware, custom software where as android will run on a multitude. Can't have 1 size fits all without compromise.
I will still say that iPhones are 110% to the power of 100 not worth the money in any way, but I'm sick and tired of seeing people compare iPhone to android when it's like comparing apples to oranges -,-3 -
YGGG IM SO CLOSE I CAN ALMOST TASTE IT.
Register allocation pretty much done: you can still juggle registers manually if you want, but you don't have to -- declaring a variable and using it as operand instead of a register is implicitly telling the compiler to handle it for you.
Whats more, spilling to stack is done automatically, keeping track of whether a value is or isnt required so its only done when absolutely necessary. And variables are handled differently depending on wheter they are input, output, or both, so we can eliminate making redundant copies in some cases.
Its a thing of beauty, defenestrating the difficult aspects of assembly, while still writting pure assembly... well, for the most part. There's some C-like sugar that's just too convenient for me not to include.
(x,y)=*F arg0,argN. This piece of shit is the distillation of my very profound meditations on fuckerous thoughtlessness, so let me break it down:
- (x,y)=; fuck you in the ass I can return as many values as I want. You dont need the parens if theres only a single return.
- *F args; some may have thought I was dereferencing a pointer but Im calling F and passing it arguments; the asterisk indicates I want to jump to a symbol rather than read its address or the value stored at it.
To the virtual machine, this is three instructions:
- bind x,y; overwrite these values with Fs output.
- pass arg0,argN; setup the damn parameters.
- call F; you know this one, so perform the deed.
Everything else is generated; these are macro-instructions with some logic attached to them, and theres a step in the compilation dedicated to walking the stupid program for the seventh fucking time that handles the expansion and optimization.
So whats left? Ah shit, classes. Disinfect and open wide mother fucker we're doing OOP without a condom.
Now, obviously, we have to sanitize a lot of what OOP stands for. In general, you can consider every textbook shit, so much so that wiping your ass with their pages would defeat the point of wiping your ass.
Lets say, for simplicity, that every program is a data transform (see: computation) broken down into a multitude of classes that represent the layout and quantity of memory required at different steps, plus the operations performed on said memory.
That is most if not all of the paradigm's merit right there. Everything else that I thought to have found use for was in the end nothing but deranged ways of deriving one thing from another. Telling you I want the size of this worth of space is such an act, and is indeed useful; telling you I want to utilize this as base for that when this itself cannot be directly used is theoretically a poorly worded and overly verbose bitch slap.
Plainly, fucktoys and abstract classes are a mistake, autocorrect these fucking misspelled testicle sax.
None of the remaining deeper lore, or rather sleazy fanfiction, that forms the larger cannon of object oriented as taught by my colleagues makes sufficient sense at this level for me to even consider dumping a steaming fat shit down it's execrable throat, and so I will spare you bearing witness to the inevitable forced coprophagia.
This is what we're left with: structures and procedures. Easy as gobblin pie.
Any F taking pointer-to-struc as it's first argument that is declared within the same namespace can be fetched by an instance of the structure in question. The sugar: x ->* F arg0,argN
Where ->* stands for failed abortion. No, the arrow by itself means fetch me a symbol; the asterisk wants to jump there. So fetch and do. We make it work for all symbols just to be dicks about it.
Anyway, invoking anything like this passes the caller to the callee. If you use the name of the struc rather than a pointer, you get it as a string. Because fuck you, I like Perl.
What else is there to discuss? My mind seems blank, but it is truly blank.
Allocating multitudes of structures, with same or different types, should be done in one go whenever possible. I know I want to do this, and I know whichever way we settle for has to be intuitive, else this entire project has failed.
So my version of new always takes an argument, dont you just love slurping diarrhea. If zero it means call malloc for this one, else it's an address where this instance is to be stored.
What's the big idea? Only the topmost instance in any given hierarchy will trigger an allocation. My compiler could easily perform this analysis because I am unemployed.
So where do you want it on the stack on the heap yyou want to reutilize any piece of ass, where buttocks stands for some adequately sized space in memory -- entirely within the realm of possibility. Furthermore, evicting shit you don't need and replacing it with something else.
Let me tell you, I will give your every object an allocator if you give the chance. I will -- nevermind. This is not for your orifices, porridges, oranges, morpheousness.
Walruses.16 -
Golang tutorials trying to explain the difference between concurrency vs parallelism be like "Oranges are different from oranges. Oranges are juicy while oranges are juicy. They are not to be confused, u newb"1
-
Didn't see any rant about Apple's new declarative UI framework: SwiftUI. Looks a lot like Flutter, but I'm still new in flutter so I'm not sure that way of creating UI, why is it better that way? Or it is just like Oranges and Apples, choose what fits your needs?9
-
I get so tired of people hating on PHP, Javascript and promoting Python or C#/Java.
Python is basically Perl with slightly different syntax plus has py2/py3 issues. And suffers from pip like js does from npm.
Java/C# started as application languages, while PHP started in web servers (again from Perl but at least it now has full object support). So comparing apples and oranges is one thing.
Another one is that people don't seem to know much about PHP / js (and tbh not even about the languages they are promoting) when they try to hate. That just comes off as lazy and borderline idiotic. Don't be that guy.
If you have had a bad experience, maybe you need to open the documentation instead of copying code from stack overflow.
Again, lazy and unprofessional.
Devs are supposed to be able to find the most efficient solution, that takes as little code as possible, not as little time from them when they arent familiar with the subject.
Damn Im angry right now, this rant really worked me up! :D6 -
Telling the customer it's not a system problem but their end users network problem over and over with proof and still making a fuss over it. What the hell do I do next?1