Recently a friend of mine pointed me towards HTTPie, a currently free Postman alternative which feels quite similar but less bloated. Also, besides the desktop app they've built a CLI client supporting form submissions and what not which is super fun to use. I personally prefer working with UIs in most cases but judging from GitHub with 32k stars as of today there might be some folks that feel a little different about the CLI topic.
@Crell while back i tried to explain that it was sort of kinda ok for the web app home page, but the api has no reason to be """user friendly""" in this manner... and that caught me shit for like 3 years >_>
now that everyone forgot i should go tweak the httpd conf and tell nobody. its like 3 lines to make apache to not do that to /api/ lmao. sadly they will still have attempted the transmission though.
@josh Well, it's not just react vs web components.
They also rearchitected their code; and as a side effect of moving away from react, they can have code optimized for the most recent Edge when react needs to support many more browser engines and versions (something you definitely want for most web apps).
@mahryekuh Regarding the mandatory "they have their place": I'd argue that React's ONLY place is at Facebook for their internal needs, and even though, they'd be better served by another tool.
React is a bad choice for 99% of the tasks its used for.
so you can't tell XHR requests not to follow redirects (but just return them instead) and Fetch requests don't have a progress api. This seems a bit broken. I'm now sending a xhr=true query to my back end and redirecting or not based on that, clunky.
If you're considering coming you can get 10% off with the code 'Friends10', making the price just ~£140 ex VAT. Student tickets are also available for £60 – exceptional value! Full details 👉 https://pixelpioneers.co/
The #PremierInn free WiFi is so bad it should become the new standard for testing website over slow connections. They /really/ want you to buy the upgrade.
Ich mag eine #Website machen, möglichst reines #HTML 4, möglichst ohne #Javascript. CSS 3 wenns sein muss, sonst eher 2.
Die Website soll möglichst auf Chrome genauso laufen wie auf Netscape (die Älteren werden sich erinnern...) und auch in Text-Browsern wie Lynx oder w3m.
tl;dr: Die Seite soll auch noch funktionieren, wenn javascript und css ausfallen.
Wie würde ich da denn "Tabs" machen? Oder was wären Alternativen zu tabs?