341–350 of 364 posts
This is more of a joke answer, but r/ProgrammerHumour recently underwent a spate of submissions competing to come up with the wackiest and "wrong" ways to do common UI elements, such as the slider or phone number inputs. A small album of the best and worst of these submissions: https://www.reddit.com/r/ProgrammerHumor/comments/6fdl8h/an_...
Earlier quoted context omitted.
How do you know what CPU my HTTP requests need?!
If your HTTP requests are high CPU and your doing standard crud type actions, there's something wrong with your codebase. High CPU tasks should be offloaded from the HTTP request into a queue.
I like http://zombo.com/ You can do anything at zombocom
Earlier quoted context omitted.
If your HTTP requests are high CPU and your doing standard crud type actions, there's something wrong with your codebase. High CPU tasks should be offloaded from the HTTP request into a queue.
Who said I was doing standard CRUD, and it seems like now you're defining HTTP requests as low-CPU activities just to make Lambda not fit explicitly. Nothing wrong with doing high-CPU activity in a request/response cycle if it's consistent and timely.
For the vast majority of crud based web apps that I've seen or worked on in the last decade, lambda would not have been a good fit. There's a lot of people drinking the serverless koolaid right now and applying it to scenarios that don't fit it well.
I once worked at Chase Manhattan Bank and one of their internal networking teams had a web site for wiring requests. They didn’t want to work too hard so their UI was designed to make data entry as slow as possible, mostly by using huge multi-level drop down lists where the slightest twitch would make them collapse and you would have to start over navigating through them, repeat a dozen times for every run of cable,…
Heroic! Lotus Notes was such a pile of junk. Every time I used it for the simplest task, the combative UI would cause my blood pressure to spike up. I would calm myself down by imagining the blissful life of the ex JPMorganChase IT boss who greenlighted the purchase, living off his giant kickback on some Caribbean island.
It took just one slip of the finger to...
I once worked at Chase Manhattan Bank and one of their internal networking teams had a web site for wiring requests. They didn’t want to work too hard so their UI was designed to make data entry as slow as possible, mostly by using huge multi-level drop down lists where the slightest twitch would make them collapse and you would have to start over navigating through them, repeat a dozen times for every run of cable,…
>(dates this) Unfortunately, it doesn't. https://www.hcltechsw.com/wps/portal/products/products-home/...
Go spend 5 minutes here on pc desktop. http://cyberspaceandtime.com/Gaano9Y6KAU.video+related I came across this site a few weeks ago. And it's quite unlike anything I've seen. And try to inspect the site using browser inspector. It's a very different ui than I've ever seen before.
Seems completely broken in Firefox and Safari, and mostly broken in Chrome/Chromium - just what browser does the site work with?
I created this SVG-based graph layout GUI [1] for our learning media website LunchBox Sessions [2]. The graph lets us visually express the prerequisites of each session. Using SVG meant I could do some fun animations to hide the load time when opening a session. [1] https://lunchboxsessions.com/explore/hydraulics [2] https://lunchboxsessions.com
That's pretty spiffy! How'd you do the layout? I was looking at elkjs [1] and the Klay layout algorithm to do something similar. [1]: https://github.com/OpenKieler/elkjs
Earlier quoted context omitted.
Who said I was doing standard CRUD, and it seems like now you're defining HTTP requests as low-CPU activities just to make Lambda not fit explicitly. Nothing wrong with doing high-CPU activity in a request/response cycle if it's consistent and timely.
Sounds like in your case lambda might be a good fit? I'm not really sure because you're not really explaining your use case. For the vast majority of crud based web apps that I've seen or worked on in the last decade, lambda would not have been a good fit. There's a lot of people drinking the serverless koolaid right now and applying it to scenarios that don't fit it well.
Have you actually built a lambda backed web service? Guessing no, or you'd know better than to complain about price. Plenty of better arguments to be had than the one lambda actually does decently on...
Earlier quoted context omitted.
No! It cannot be that Agresso was already around at that time. I still have to work with that horrific system, even though it is webbased now. It's still a horrible experience.
> There was an appalling timesheet system called Agresso, the most counterintuitive Windows GUI I ever encountered. I love the idea that there was a terrible timesheet system called Agresso. And that it's still around today! Some things do change with time. If this system was created today, I imagine it would be named something like quiesso or daisy.
Small world