fleshweasel posted:

basically if your org is ie9 or earlier you're looking at bootstrap.

Maluco Marinero posted:

it's concerning how much stock developers put into not understanding css. or at least, they want a framework to 'take the pain of css away', missing that most frameworks aren't nice clean abstractions of CSS and thus don't really obviate the need to actually understand CSS unless you follow their examples.

I guess what I'm saying is, it'd be real swell if people acknowledged that maybe having someone on staff who actually knew how CSS worked, how it's used to achieve standard design patterns, and could dictate best practices. maybe then CSS wouldn't be this inscrutable language of mystery it seems to be for most people.

I'm not saying CSS is a good language, far from it, but like if you had a MUMPS codebase, you don't suddenly turn around and get a developer who knows nothing about the lang to make fundamental implementation decisions.

comedyblissoption posted:

the problem with css is it wasn't designed properly for common UI lay out concerns for graphical applications and you had to learn a bunch of hacks and "css tricks" for what should otherwise be straightforward concerns. of course people are going to get frustrated having only absurd hacks as their primitives for composing what they want.

a lot of the "css frameworks" like bootstrap are a blessing because they help get you some basic layouts without having to learn absurd hacks.

even flexbox alone isn't good enough for general purpose layout

afaik region based layouts are still experimental poo poo

Share Bear posted:

is there something that's really good at doing async http requests in java because apache-commons is annoying horseshit

i just gotta blast off like a million rest updates, in java

this is to replace a script written with asyncio in python

Share Bear posted:

is there something that's really good at doing async http requests in java because apache-commons is annoying horseshit

i just gotta blast off like a million rest updates, in java

this is to replace a script written with asyncio in python

Sapozhnik posted:

Throws the checked InterruptedException like most other multithreading things in Java. It's consistent at least, but it's still a pain.

Signals any and all failures using ExecutionException. This alone turns any error handling involving standard Futures into a godawful mess because you have to disentangle the cause of the exception manually instead of using multiple catch blocks. And you have to catch ExecutionException whether or not what you're doing can actually fail. There are limits to what you can do with Java here but defining Future as interface Future<T, X extends Throwable> { T get() throws X; } would have done a lot to mitigate this problem (you can e.g. set X to RuntimeException if you don't want the client to have to deal with any checked exceptions at all).

Not natively chainable until Java 8. This imposes some nontrivial constraints on the implementation (making futures chainable means that a client is able to seize a potentially unbounded amount of execution time from your thread, so you either need to host a thread pool for this purpose or be very clear about your expectations around non-blocking IO or whatever) but a non-chainable future is almost useless. The whole point of futures is to put some structural lipstick on callback functions, after all.

The way they added chaining is pants-on-head retarded. Instead of defining a ListenableFuture<> derived interface like literally every single async IO framework for Java did (see Netty et al) they created a concrete CompletableFuture class. This thing has a bajillion methods for some reason and in addition to allowing clients to chain off of a CompletableFuture completion it also allows those same clients to fulfill the promise

I'm sure you could design a worse standard Future type if you put your mind to it but loving it up to an even greater extent would be legitimately challenging. As it stands it would be almost impossible to retrofit into a c# style async/await mechanism further down the road, if for no other reason than the compiler cannot guarantee anything about an async operation's exception specification.

HoboMan posted:

still better than that same person crashing the filesystem (and server) by spamming a 2 mb xml every second into a random folder somewhere

Luigi Thirty posted:

bad news: I can't get the C standard library to work yet

ulmont posted:

You might want to try newlib - it's a smaller standard library designed for embedded systems that builds for a number of systems including 68k ones.

It's also the C library cygwin uses.
https://sourceware.org/newlib/

MALE SHOEGAZE posted:

I have some sort if spatial impairment and I have to close my eyes and think really hard to remember which element is vertical and which is horizontal in a coordinate pair (and then I have to figure out what horizontal even means, man). So, luigis adventures in 3d programming make me sick to my stomach.

Sapozhnik posted:

the horizon is horizontal dood

Sapozhnik posted:

the horizon is horizontal dood

Luigi Thirty posted:

+X is right
+Y is up
+Z is into the screen

VikingofRock posted:

Ewww, left-handed coordinates. Is that standard in graphics programming?

Luigi Thirty posted:

Terrible programmer status: better than whoever did this

https://twitter.com/robotlolita/status/845361020038266880

Luigi Thirty posted:

Wheany posted:

that taskbar? dock? texture, tho

Share Bear posted:

is there something that's really good at doing async http requests in java because apache-commons is annoying horseshit

i just gotta blast off like a million rest updates, in java

this is to replace a script written with asyncio in python

Luigi Thirty posted:

every 90s operating system needs a clone of the nextstep dock

the texture is bad because it's a 256-color image and the desktop is set to 16 colors because OCS

Sweevo posted:

ditch the crappy dock and use ToolsDaemon to put all your most-used software in a menu.

PokeJoe posted:

assertThat(myAss).contains(dicks);

comedyblissoption posted:

if youre writing tests make sure the only things you ever mock are interfaces external to your program (e.g. file system, network calls). mocking too much and having a bunch of useless tests is a very common trap

someone told me that you shouldn't even mock at all and design your program so it's easy to test everything w/o even calling out to external systems. i dont have experience w/ this at all but maybe he's right.

fleshweasel posted:

this sometimes works. all you do is write a deterministic function that does your business logic, then write a wrapper function that does I/O or network poo poo and then runs your business logic on the stuff that come from disk or network. it falls short when you conditionally need to do a fetch based on the results of another fetch, etc. because you either have to just fetch everything upfront or do some kind of sequencing in your function that directly touches I/O that pretty much turns it into a business logic function.

AmigaOS 3.1 posted:

Flood fill is a technique for filling an arbitrary shape with a color.
The Amiga flood-fill routines can use a plain color or do the fill using a
combination of the drawing mode, FgPen, BgPen and the area pattern.

Flood-fill requires a TmpRas structure at least as large as the RastPort
in which the flood-fill will be done. This is to ensure that even if the
flood-filling operation "leaks", it will not flow outside the TmpRas and
corrupt another task's memory.

fleshweasel posted:

it falls short when you conditionally need to do a fetch based on the results of another fetch, etc. because you either have to just fetch everything upfront or do some kind of sequencing in your function that directly touches I/O that pretty much turns it into a business logic function.

redleader posted:

why are you asserting against a constant value

Ator posted:

from Living Clojure, chapter 5

Here’s an illustration of each naming convention:

this_is_snake_case

this-is-kebab-case

ThisIsCamelCase

edit: oops, meant to post this in the lang thread. oh well