6 ms·
Last time I checked, the problems facing web developers were(in no particular order): Rendering HTML templates / JSON Asset compilation / Cache busting Cachi
by dham 11y ago
Last time I checked, the problems facing web developers were(in no particular order):
Rendering HTML templates / JSON
Asset compilation / Cache busting
Caching
Sending Email
Previewing/Testing Email
Background Job queuing(with failure/retry/backoff)
Reliable and easy integration/feature testing
Connecting to database and modeling data
Authentication / Account signup / Confirmation / Forgot Password
Security
Payment handling
PDF / Invoice rendering
Deployment
Making pretty good money over here and how many ROFL scale GO routines I can run never really came up.
¯\_(ツ)_/¯
- stevewilhelm 11y ago> Authentication / Account signup / Confirmation / Forgot Password +1 And Authorized data access.
- codepie 11y agoI posted[1] asking specifically about this, a couple of days ago. But didn't get any response. [1] https://news.ycombinator.com/item?id=11152976 https://news.ycombinator.com/item?id=11152976
- redtuesday 11y agoIs djangos default authentication and authorization [1] not enough (since you mentioned django in your post)? If so you could take a look at django-allauth it seems [2] or maybe at Stormpath [3] (external service) or ABAC [3] (which is probably total overkill, too enterprisy and is only used for authorization as far as I know). [1] https://docs.djangoproject.com/en/1.9/topics/auth/ https://docs.djangoproject.com/en/1.9/topics/auth/ [2] http://www.intenct.nl/projects/django-allauth/ http://www.intenct.nl/projects/django-allauth/ [3] https://docs.stormpath.com/python/ https://docs.stormpath.com/python/ [4] https://github.com/cedadev/ndg_xacml https://github.com/cedadev/ndg_xacml
- Zikes 11y agoLots of people making pretty good money developing in whatever language best suits their environment or problem at hand. ¯\_(ツ)_/¯
- deleted 11y ago[deleted]
- tie_ 11y agoEven more people are making good money developing in the language/tooling they know/favor, while it is (comparatively) poorly suited to the problem at hand.
- hdra 11y agoYou forgot jumping on the hype bandwagon and getting a piece of the hype-rush. Seriously though, Go is a really good language. Its a simple yet solid & powerful language, but why would people feel the need to present it as the silver bullet for everything?
- twic 11y agoDon't forget binding posted form data to a model, and then validating it. It seems like 60% of my web development time is spent getting that right.
- webjunkie 11y agoGotta love Django's ModelForms
- romanovcode 11y agoYou should try ASP.NET, it will reduce your 60% to about 2%.
- deleted 11y ago[deleted]
- diminish 11y agoHere a list of why OP's list of advantages of Go for web developers: * Static typing * Web sockets * Concurrency * Unit testing * Speed * Syntax * Formatting tools
- pjmlp 11y agoMy web development experience, apart from an experience with TCL that teached me never to rely on scripting languages for serious web applications, is on the JVM and .NET stacks. Both eco-systems fill all those bullet points.
- cmdkeen 11y agoBy night I might play with Django and like it. By day I make good money using C# where I get all of the above at what seems to be a much more web appropriate level than Go. One of the things that I'm really liking about the ASP.Net Core rewrite is that a framework that has been around for ages is taking an opportunity to look at what it does well, what it doesn't and what other languages / frameworks have innovated on more recently and stealing liberally. C# has been through several cycles of how to write concurrent code now and offers both Task and async/await depending on your needs. Not only is web sockets support there but SignalR is there as a useful API for common cases. If you want even better static typing you can switch to F#. Not everyone was doing web development using single threaded dynamically typed languages before Go came along.