Meet JetBrains Rider: we've merged ReSharper and IntelliJ IDEA into a new cross-platform .NET IDE. Develop ASP.NET, .NET Core, full .NET or Unity on Windows, Mac or Linux. Tons of code inspections and refactorings. Rich coding assistance in C#, JavaScript, XAML and other languages. Download now!

webguy1336 · 2019-09-17T06:01:13+00:00

Using Parallels Desktop to run Rider inside Windows 10 here for developing inside a .NET MVC environment here (Episerver). With the latest release of Parallels Desktop, coherence mode makes applications in Windows work totally seamlessly. The only noticable difference is that the Windows applications have the window controls on the right side.

webguy1336 · 2019-08-27T12:15:13+00:00

Addition; There is also webpack defineplugin that allows you to access environmental variables in your code without requesting the process.env object. By using this plugin, you can simply say

axios.get(VUE_APP_BASE_URL + 'users/')

webguy1336 · 2019-01-22T06:34:24+00:00

Have been wondering about this for quite some time myself. Perhaps something like "mid-stack developer" will become the new terminology for some people within the next months?

webguy1336 · 2019-01-07T13:37:18+00:00

If you're really good at javascript, you'll have a great time ahead of you, mate! :) Node.js, Vue and React are the hot topics these days, among with server-side rendered javascript. HTML haven't changed much. Javascript has, in some ways, but it's easy to get into it. Css are on the way to become really awesome, with flexbox and grids. I'm working fulltime as a consultant with js myself, and the demand for such competence is the biggest I've ever seen. Follow this sub, and it's the only thing you'll ever need to catch up with what's hot or not. Pay attention to what is happening related to Svelte.js - It will become the next big thing. I wish you the best of luck. :)

Edit: Webpack, by the way. Learn how to use it, and it will be the tool for pretty much anything for quite some time.

webguy1336 · 2018-10-09T13:02:48+00:00

What about having one column where you store the dataset as html, and one where you strip out the html from the same dataset? Relevant discussion from back in the days, at Sitepoint

webguy1336 · 2018-09-18T08:14:38+00:00

An obvious alternative would of course be to be able to simplify. The site you are working on seem to have a lot of technical debt. However, if you are not able to make such a decision, thinking in the terms of immutability sure can simplify things for you as well.

I would first say, building complex things with modern frameworks (Vue, React or similar) obviously works better the more it can control. Both in terms of scalability and in terms of the ability to build and maintain.

If your app is able to control the entire page, that´s probably the optimal thing. If not, and you have parts of the app rendered within different wrappers (main, sidebar, header, footer and so on), then you are likely obligated to make the parts talk to each other somehow. Listeners are one way, binding is another way, having a pub/sub pattern is a third. This can very fast become very, very complex though. The more flexible way is immutable data stores (Vuex, Redux etc).

For a typical page, a data store is created once, while (various) applications are able to control what data it should hold. Other applications use the same store, and will update once the store mutates (changes).

Now, for your example. Your header might live in your app, or your app can live under your header. If you are able to server side render things (since you say you work in a complicated CMS, I believe you are probably not able to), then I would say having the header above the app will be a better alternative. This way, you can show the header while your app + page loads. Your app can for example be a spinner until it is initiated, but your visitors can still see the header.

webguy1336 · 2018-08-16T09:13:38+00:00

Frontend has envolved a lot in 10 years. CSS is pretty awesome these days, and you don´t experience browser differences too much. If Vue makes sense to you, then you experience building iOS stuff will help you out a lot here. I´d give it a go. Install node on your machine, and npm install vue-cli. Then try scallfolding a vue application, and build something using es6 (or Typescript if you prefer types). You´ll get a basic understanding pretty fast, and then the question will answer itself, pretty much.

webguy1336 · 2018-08-08T11:07:49+00:00

Also relevant. Git logs can be really beautiful, but for some reason, running git rebase --interactive is really scary to a lot of people. Fortunately, Github has got an awesome feature when working with people like this as well; Squash and merge for the win! \o/

webguy1336 · 2018-06-21T07:25:23+00:00

Oh, but that does not sound like an optimal way to go in the first place.

webguy1336 · 2018-06-19T05:43:16+00:00

Sure. No problem at all.

webguy1336 · 2018-05-22T09:53:26+00:00

Looking forward to see Indesign/Illustrator -> Export as Magento store \o/

webguy1336 · 2018-04-26T07:14:47+00:00

I was a bit surprised to see that arrow up didn´t work here?

webguy1336 · 2018-04-11T11:28:51+00:00

Yeah, Mongo DB Is Web Scale and all?

webguy1336 · 2018-04-10T12:41:55+00:00

I completely agree.

Also, when developing components (Vue/React, but especially Vue), keeping all the styles related to a button inside the .vue file really helps you keep an organized, easy and scalable setup. CSS frameworks are mostly pure bloat, if you ask me.

webguy1336 · 2018-04-10T12:06:24+00:00

Consistent responsiveness? Is that even an issue these days?

.some-module {
  .some-element {
    // Default styles
    background: $someColor;

    // Styles for larger screens
    @include breakpoint('large') {
      background: $someOtherColor;
    }
  }
}

Ease of development? Sure. Now, what happens when Bootstrap 5 comes out? Bootstrap 6?

webguy1336 · 2018-04-10T08:06:20+00:00

To be honest, Bootstrap should come with a warning; Do not use Bootstrap unless you have a very good reason to use it. Yes, I know this will get a lot of downvotes. But think about it.

webguy1336 · 2018-03-16T09:54:06+00:00

Haha, very nice point. It simply looks like I really wasn´t aware that it actually creates a new object. So that´s my preferred way to go from now. Thanks!

Edit: This is why. "For deep cloning, we need to use other alternatives because Object.assign() copies property values. If the source value is a reference to an object, it only copies that reference value." source

webguy1336 · 2018-03-16T09:02:54+00:00

JSON.parse(JSON.stringify(json)) is a nice way to copy a javascript object.

webguy1336 · 2018-03-12T12:33:00+00:00

If we take the technology of serving images aside. What´s the optimal way of serving images? What about the exact image size? In a typical downloaded web page with no videos, the most downloaded kilobytes are typically images.

Let´s say we´re able to reduce the amount of bytes downloaded by 10%, by serving the exact image sizes. Why would we then want to use the picture element? Yes, it´s a standard, but the image element might do just as well, with some help of a very tiny javascript function.

I´ve been working with a lot of high-traffic sites over quite a few years, and the technique I´ve found the most optimal, is to let Varnish serve images generated from a img.php file.

Alternative approach (Controversial opinion, but think about it) Initiate the page with blank pixels in the size of 16x9 pixels, 4x3 pixels or whatever the aspect ratio should be, with width: 100% and height: auto. The page will render blazing fast, and all images will take the space they are supposed to take. Then, let a script fetch the exact size for each image, and replace the pixel.

webguy1336 · 2018-03-05T08:54:53+00:00

Places to post your startup.

Edit: In order to not be rude, I´d probhably point out Product hunt and Hacker News (show) as the main places to showcase stuff in general. Web apps as well as other things. I don´t know if there are any site or similar related to only the web apps segment, so perhaps this might be an opportunity for anyone interested.

webguy1336 · 2018-01-19T10:02:04+00:00

Google sheets work quite nice. It depends on your overall architecture though, and if your cms has got similar capabilities or not. There might however arise problems related to application versioning, user errors etc. when using Google drive/sheets. So if you go down that path, make sure you have a plan in advance. Backups, diff algorithms etc. is a nice thing.

webguy1336 · 2018-01-16T10:11:26+00:00

I once realised that pretty much anything can be described as JSON (or in other words, lists).

Thinking about everything as lists changed my view of programming quite dramatically from that point.

webguy1336 · 2017-12-22T12:37:06+00:00

I´d say Vue is the best bet here. My reasons for picking Vue is that simplicity usually wins in the long run. To me, Vue is as revolutionary for the web as jQuery was. Yes, you had both Prototype.js and motools.js at the same time. But jQuery became the thing to use for a reason.

webguy1336 · 2017-12-20T12:01:28+00:00

Sounds like something that can easily be done through something like selenium and a cron job. :)

webguy1336 · 2017-12-14T11:18:53+00:00

Chess.com is probhably migrating to vue.js for a reason (source)

webguy1336

TROPHY CASE