Live data from Hacker News

WordPress on .NET

peachpie.io

131–140 of 174 posts

Re: WordPress on .NET

#132
post #116

Earlier quoted context omitted.

May I ask why?

PHP and the overall quality of average WP code?

Honestly, I think I'll take 'average' php code over 'average' .NET code, I just did a 18 mo. stint at a .NET enterprise environment after 8+ yrs of PHP(Drupal, so maybe the bar is higher, not saying it is, but maybe).

Re: WordPress on .NET

#133
post #116

Earlier quoted context omitted.

PHP and the overall quality of average WP code?

Honestly, I think I'll take 'average' php code over 'average' .NET code, I just did a 18 mo. stint at a .NET enterprise environment after 8+ yrs of PHP(Drupal, so maybe the bar is higher, not saying it is, but maybe).

I don't have any substantive evidence for this, but I suspect you'd see very different characteristics among people who work on SharePoint and, say, MVC/WebAPI.

Re: WordPress on .NET

#134
post #90

Earlier quoted context omitted.

I would look at sitecore. It's still .net, but it is closer to wordpress in that you wouldn't necessarily build a sharepoint in it, but you can build pretty much anything else in it. Disclaimer, I work on the UX/UI side of a company that focuses solely on sitecore.

Thanks for sharing this, but what exactly does this provide that WP doesn't to justify the cost?

I'm not familiar with the product, but surely leveraging existing expertise has some value.

Re: WordPress on .NET

#135
post #11

I don't care about performance, show me if security has improved! (which in the case of Wordpress can't be that hard)

I'll do you one better. We're hosting a private-facing WordPress with several custom post types and some custom fields using ACF Pro. Then we pull directly out of the database with some not-too-complex and fast SQL queries and build a static site with Jekyll. The whole thing is about 200 lines of Ruby + a bunch of configuration for each post type. I'm working on making this a little more generic, because this thing r…

How are you handling all the rendering that WP needs to do on a post (e.g. shortcodes, special HTML formatting, etc)? ... or are you just forcing your users to write Kramdown and leaving out things like shortcodes? IMO, the worst parts about Wordpress are: 1) complete coupling of data to PHP and 2) the absurdly terrible DB schema.

Re: WordPress on .NET

#136
post #116

Earlier quoted context omitted.

PHP and the overall quality of average WP code?

Honestly, I think I'll take 'average' php code over 'average' .NET code, I just did a 18 mo. stint at a .NET enterprise environment after 8+ yrs of PHP(Drupal, so maybe the bar is higher, not saying it is, but maybe).

I started out as a PHP web developer and started developing in .NET when it was released. At this stage, I've been developing applications in .NET for 15 years. Whenever I have to look at a PHP project or ASP classic project, the code quality is usually much worse than other languages. ASP and PHP make it really, really easy to do things wrong.

Re: WordPress on .NET

#137
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.

Perhaps, but WP also has a large user base from which to pull from so I would hope vulnerabilities get discovered and patched quickly. However, I think it's quite telling that such a popular project still has issues with SQL injection even with so much active development apparently going on.

Re: WordPress on .NET

#138

Earlier quoted context omitted.

I laughed at that. As much as I still shun MS platforms, I have never heard anything good about PHP as a language other than "it worked and was available at the time". Why someone would migrate in this direction is beyond me ;-) but that's just my opinion of course.

Critical mass, availability of developers, good documentation, free. There are many reasons why people pick one technology over another.

Cheap for employers is what i'm hearing, but isn't really an incentive for an employee..

Re: WordPress on .NET

#139

Earlier quoted context omitted.

Honestly, I think I'll take 'average' php code over 'average' .NET code, I just did a 18 mo. stint at a .NET enterprise environment after 8+ yrs of PHP(Drupal, so maybe the bar is higher, not saying it is, but maybe).

I don't have any substantive evidence for this, but I suspect you'd see very different characteristics among people who work on SharePoint and, say, MVC/WebAPI.

Vastly. People who develop sharepoint tend business focused people or ex IT people.

People who develop in MVC tend to be developers.

Re: WordPress on .NET

#140

Earlier quoted context omitted.

Honestly, I think I'll take 'average' php code over 'average' .NET code, I just did a 18 mo. stint at a .NET enterprise environment after 8+ yrs of PHP(Drupal, so maybe the bar is higher, not saying it is, but maybe).

I don't have any substantive evidence for this, but I suspect you'd see very different characteristics among people who work on SharePoint and, say, MVC/WebAPI.

[deleted]
Post reply on HN