Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>How does it compare to the mysql one or MS sql server management studio for that matter?

It dosent compare, but then when working with php and mariadb you dont often use the advanced/esoteric features you have in SQLserver

>Wamp installer is windows specific but i'd assume you browse to find the download for it, etc or use winget or chocolately instead of sudo install xyz, etc so i fail to see the advantage there?

Well there is less configuring with wamp and there are gui tools to manage things, installing the services in linux and setting them up is always a bit more work. I have never tried xampp in linux so it might be equal there.

>There's a reason people jokingly call it microsoft java. The second half might be mischaracterizing it on many fronts but the first half is true to form. I'd argue it as an argument in this matter is similar to bringing up the best platform for developing with Swift.

It being an complete integrated package from the OS to the IDE is the best feature about dotNet. You can look at it the same way as "the lisp machine" but with better third party software support. I guess swift has the same benefits, altho when i tried it the tools where not really up to the same standards as visual studio.

I have yet came across a language platform i cant develop with ease on windows. Also these days with tech such as docker etc there really are no boundaries.



>It being an complete integrated package from the OS to the IDE is the best feature about dotNet.

In a general purpose development context I consider it a downside. In the same way that I don't consider it a boon for XCode & the like that I can't run it on my machine and will need to go buy a mac.

When it comes to a more general purpose development context I find that a lot of things have this "if you are on windows" asterisk. From recent memory it can go from the rustup installation page just referring to a completely different page or rediscovering that text files having diverging line endings there or needing to do some workarounds when making commandline tools in such low level languages so that they'll also work on windows, needing to bundle some redistributable dll in your installer to make things work on windows even if you used visual studio on windows to make your binary. They'd work everywhere except windows because vcruntime isn't statically linked by default or something. Given PHP being mentioned think this was also the reason it took so long for various PHP functions to become available on windows in the past (Not sure if they're all available now. I haven't kept up). I remember discussions from back then with complaints about Windows being a second class citizen for php when that wasn't really the case rather it was just more often the odd one out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: