|
simble posted:you just need enough reputation and you can do stuff if you dont have enough fake points it gets put into a queue where its approved/denied by morons with enough points
|
# ? Mar 21, 2019 02:03 |
|
|
# ? Apr 25, 2024 11:40 |
|
Shaggar posted:setting specific versions for libraries is pretty normal and allows you to build the same thing again reliably. allowing any version can introduce unexpected changes in functionality There is nothing in the code that requires super specific versions, and even if a new version of a dependency library broke something, I would then agree to do a <= on the requirement. Or fix the issue and update the version.
|
# ? Mar 21, 2019 02:07 |
|
okay, but how is carrying on using the version that worked yesterday suddenly going to break things?
|
# ? Mar 21, 2019 02:17 |
|
Lutha Mahtin posted:is this the first time you've encountered an inversion-of-control MVC framework? i had a similar reaction when i first tried to learn android but it makes more sense the more you read about how apps work in android. either way it's how the android API is structured so you will pretty much have to learn to live with it I've seen MVC stuff before but this setup feels excessively abstracted. We've got a settings activity that dynamically loads in some SettingsFragments and SettingsSomethingFragments inside there too. The injection stuff and magic view binding annotations on top of all that make it hard to see where the stuff that gets put into the view is even specified. If it was regular code I could use the IDEs find usages search or similar, but magic @ annotations seem to mess that up since they generate code at build-time. Anyways the stuff I was looking for ended up being in an xml config file that wasnt mentioned in any of the view or presenter classes
|
# ? Mar 21, 2019 02:30 |
|
I think when it comes to abstraction, people tend to focus on how the abstraction is done rather than what the abstraction achieves. I.e. good abstraction: you get in your car and can accelerate, turn left, right, break etc without actually knowing how your car works. Most software abstraction: you get into the car and there's two buttons only, "OFFICE" and "AIRPORT". you're now tasked to build a machine that will alternatively hit both buttons until you reach "SHOPPING CENTRE". You cannot build a third button because if you do, you might as well build a new car. A co-worker is on a tricycle screaming about microservices.
|
# ? Mar 21, 2019 02:38 |
|
The list of menus and submenu options are all unchanging so this system of loading in fragments and then replacing them with new ones when you travel into the menu hierarchy didnt need to exist
|
# ? Mar 21, 2019 02:46 |
|
YOSPOS: A co-worker is on a tricycle screaming about microservices.
|
# ? Mar 21, 2019 04:31 |
|
python and its community are trash if they took interface stability seriously they wouldn't have created an incompatible new revision of the language and then immediately set about killing the old one that people were foolishly depending on
|
# ? Mar 21, 2019 04:47 |
|
Dijkstracula posted:YOSPOS: A co-worker is on a tricycle screaming about microservices.
|
# ? Mar 21, 2019 04:52 |
|
Dijkstracula posted:YOSPOS: A co-worker is on a tricycle screaming about microservices.
|
# ? Mar 21, 2019 07:14 |
|
Chalks posted:Commit messages that link to the work item/ticket they were assigned is always useful no matter how terrible the developer. When ever you find insane code, you always want to know what they were trying to achieve when they did it. Gonna emptyquote this
|
# ? Mar 21, 2019 08:34 |
|
Shaggar posted:setting specific versions for libraries is pretty normal and allows you to build the same thing again reliably. allowing any version can introduce unexpected changes in functionality shaggar was right
|
# ? Mar 21, 2019 08:57 |
|
Shaggar posted:wales, Scotland, etc.. are more like counties than states. please tell us more about how our own kingdom works, o wise foreigner
|
# ? Mar 21, 2019 09:01 |
|
can't wait to get my Scottish passport within the year, giving me the full trifecta Back to my twitter stuff: since there's no processing I'm not actually convinced doing the auth serverside and then the calls clientside will really save me much bandwidth. Like how big is a request with no body? E: I guess one advantage to doing it clientside would be that the user auth can stay loaded in the js, no need for it to be on the server gonadic io fucked around with this message at 09:37 on Mar 21, 2019 |
# ? Mar 21, 2019 09:24 |
|
Soricidus posted:please tell us more about how our own kingdom works, o wise foreigner Lets give it a year and see how that holds out.
|
# ? Mar 21, 2019 12:44 |
|
Sapozhnik posted:python and its community are trash
|
# ? Mar 21, 2019 13:21 |
|
if only the death of python 2 had been immediate
|
# ? Mar 21, 2019 13:24 |
|
Soricidus posted:please tell us more about how our own kingdom works, o wise foreigner not very well
|
# ? Mar 21, 2019 13:49 |
AggressivelyStupid posted:not very well depends if its main output product is or isn’t laughter
|
|
# ? Mar 21, 2019 13:50 |
also angloboos need to remember that england etc are countries in interpretation of local laws only, where uk is centre of the galaxy. for everyone else uk is one country, at least until march 29
|
|
# ? Mar 21, 2019 13:54 |
|
one would think i wrote these forums in flask in a half hour
|
# ? Mar 21, 2019 14:27 |
|
cinci zoo sniper posted:also angloboos need to remember that england etc are countries in interpretation of local laws only, where uk is centre of the galaxy. for everyone else uk is one country, at least until march 29 wait what's happening march 29? is this something to do with brexit?
|
# ? Mar 21, 2019 17:55 |
Finster Dexter posted:wait what's happening march 29? is this something to do with brexit? yeah, the current deadline. if nothing changes they are gtfo’d from eu with no agreements on that day
|
|
# ? Mar 21, 2019 18:09 |
|
cinci zoo sniper posted:yeah, the current deadline. if nothing changes they are gtfo’d from eu with no agreements on that day yikes good luck, uk friends
|
# ? Mar 21, 2019 18:35 |
|
Holy cow I sure do like programming with strings. Whose dumb idea was it to invent other types?
|
# ? Mar 21, 2019 18:36 |
|
Gazpacho posted:Holy cow I sure do like programming with strings. Whose dumb idea was it to invent other types?
|
# ? Mar 21, 2019 18:39 |
|
The real fun begins when you have to come up with your own string implementation.
|
# ? Mar 21, 2019 18:50 |
|
Gazpacho posted:Holy cow I sure do like programming with strings. Whose dumb idea was it to invent other types? This is called "stringly typed" programming.
|
# ? Mar 21, 2019 18:53 |
|
this may sound dumb but I like ruby's distinction of strings and symbols
|
# ? Mar 21, 2019 18:58 |
|
Symbolic Butt posted:this may sound dumb but I like ruby's distinction of strings and symbols Scala technically has this too code:
|
# ? Mar 21, 2019 19:24 |
|
wtf
|
# ? Mar 21, 2019 19:31 |
|
These days you do at least get the warning: suspicious variable shadowing by wildcard match 'fooVal' or something
|
# ? Mar 21, 2019 19:41 |
|
but why does butt("baz") match foo??
|
# ? Mar 21, 2019 20:02 |
|
Krankenstyle posted:but why does butt("baz") match foo?? I assume BarVal is interpreted as a constant value and therefore the case statement matches only when exactly equal, while fooVal is interpreted as a variable name, and bound to “baz” as a result of Scala’s pattern matching case statement. Hard-coding variable/constant naming conventions as a behavioral difference seems dumb and bad to me in a way syntactically significant white space could only dream of but hey, forget it Jake, it’s Scalatown.
|
# ? Mar 21, 2019 20:14 |
|
Krankenstyle posted:but why does butt("baz") match foo?? This isn't the horror, although it is a bit surprising if you haven't done much pattern matching. It's the same as if that line was "val fooVal = input", you're making a new value which shadows the old one. The horror is that this behavior changes depending on if the name starts with a capital or not since that's how a symbol is specified. As comradeCosmobot said, symbols (and string literals) match exactly.
|
# ? Mar 21, 2019 20:18 |
ComradeCosmobot posted:I assume BarVal is interpreted as a constant value and therefore the case statement matches only when exactly equal, while fooVal is interpreted as a variable name, and bound to “baz” as a result of Scala’s pattern matching case statement. now once more but slower
|
|
# ? Mar 21, 2019 20:21 |
|
gonadic io posted:These days you do at least get the warning: suspicious variable shadowing by wildcard match 'fooVal' or something In fact you might even get another warning that the third case can never be reached
|
# ? Mar 21, 2019 20:24 |
|
cinci zoo sniper posted:now once more but slower The fooVal at the top and the fooVal in the match are entirely unrelated. This is fairly typical behavior in flangs, and if you replace the match with a val or variable declaration, I would say most langs would behave the same gonadic io fucked around with this message at 20:30 on Mar 21, 2019 |
# ? Mar 21, 2019 20:28 |
|
the hosed up part, as gonadic io pointed out, is that the only reason it doesn’t work for BarVal is that the capitalized first letter (and only the capitalized first letter) makes it a symbol/constant and therefore it won’t be reassigned by the pattern match most other languages do something sane like having an sigil or explicit quoting mechanism like the apostrophe in ‘BarVal in Scheme (and Lisp?) or the colon in :BarVal in Ruby. Scala, being Scala, happens to make this call based on whether or not the first letter is capitalized.
|
# ? Mar 21, 2019 20:40 |
|
|
# ? Apr 25, 2024 11:40 |
gonadic io posted:The fooVal at the top and the fooVal in the match are entirely unrelated. This is fairly typical behavior in flangs, and if you replace the match with a val or variable declaration, I would say most langs would behave the same oh right I get what you mean
|
|
# ? Mar 21, 2019 20:41 |