WordPress on .NET • Hacker News Board

Re: WordPress on .NET

#171

Post by cutler » Wed, Mar 01, 2017, 3:42 PM UTC

blowski wrote: post #66

emodendroket wrote: post #23

Earlier quoted context omitted.

I think you might be the first case I've heard of of someone wanting to go from .NET to PHP.

Most of my work in the past few years has been migrating .NET projects to PHP for enterprise clients. Especially with PHP 7, the performance is good, it's easier to hire for, and the total cost of ownership is lower. The doomsayers predicting poor security are wrong - it is just as possible to build a secure PHP system as a secure .NET system, and just as easy to build an insecure one. Of course, it depends on the pr…

I'm a bit new to .Net but doesn't the shift to .Net Core hosted on Linux and compatible with MySQL/PostgreSQL address all these concerns?

Re: WordPress on .NET

#172

Post by jacquesm » Wed, Mar 01, 2017, 9:33 PM UTC

jmcdiesel wrote: post #169

jacquesm wrote: post #57

Earlier quoted context omitted.

I don't care what he's quoting and to see this as 'light-hearted' (without any further elaboration on the part of the OP) is extrapolation. FWIW the comment in the movie is also a negative one. > John Hammond: I don't think you're giving us our due credit. Our scientists have done things which nobody's ever done before... > Dr. Ian Malcolm: Yeah, yeah, but your scientists were so preoccupied with whether or not they…

You are far too serious a person. I actually stand by the sentiment. Wordpress is a virus, and like jQuery, it has negatively impacted the development scene of the language is lives in. PHP, on the cusp of becoming a more respectable language (I freely admit my love for PHP, to this day, even though I primarily work in Java and Python now), was taken over by WP "developers" who flooded the market and sell themselves…

The person posting this went out of his way to try to do some good. Instead of taking them down with cheap shots: What have you done to give the PHP world (better?) options?

If everybody that railed on others creations would instead spend the time to provide better alternatives then we wouldn't be having this discussion. But cheap shots are cheap and work is hard.

Re: WordPress on .NET

#173

Post by pawadu » Thu, Mar 02, 2017, 9:41 AM UTC

josefresco wrote: post #69

pawadu wrote: post #62

Earlier quoted context omitted.

not even have a very competent team can put enough lipstick on this pig: http://www.cvedetails.com/vulnerability-list/vendor_id-2337/...

What you're missing is that these security exploits are discovered, patched and disclosed. The same can't be said about most tech services / products. Security through obscurity is not a viable strategy.

What has this to do with security through obscurity??

WP security is like Whac-A-Mole, you patch one serious issue and two more pop up. It has been like this for years which shows that the developers don't have the correct mindset to write internet facing code.

I pointed you to a SQL injection / remote execution vulnerability in the WP core, in 2017 for gods sake.

Re: WordPress on .NET

#174

Post by WhitneyLand » Mon, Mar 06, 2017, 2:35 PM UTC

WhitneyLand wrote: post #42

This is a great way for Microsoft to show the potential of and build awareness for .NET core, I hope they are helping these guys. The nuget thing is inefficient, MS should plot a path to make npm a first class citizen in all ms tools.

>NPM is already supported by default for quite some time in VisualStudio

I should have been more clear. I mean MS should work with Node/LAMP people to invest in one package manager more than the other. Like they did with TypeScript, they didn't just build a tool that linux people never used, they made useful tooling and also spent a lot of time bringing Google and others into the fold.

It makes sense to back npm because (guessing) it's used more than nu-get is used by VS devs. However if nu-get has a stronger ecosystem, stronger user base, etc choose it.

Having competition is usually good, but sometimes it just means it's more work to have to learn more/work more to get the same thing done (if you work across environments). Take instant messaging protocols, lots of competition but not even having cooperation has made the result terrible. Incompatibility everywhere, reinventing the wheel, etc.

To be sure some things are better not unified. We have multiple, un-unified browser engines and implementations which is critical. It improves competition, innovation and quality while still allowing surface level standardization in html/css/etc.

I try to look at each set of competing projects independently and ask: Overall is this helping, or it is mostly just wasting time as clients are forced to learn multiple techs.