Blog.
Hi, my name is Marco. Working as a Senior Software Architect at Philips. I'm an Opensource Maintainer and Contributor. If you like my work, consider to sponsor my work.
I wrote my first blog March 2011. Mostly I'm writing on software development. In total I wrote 75 articles in 7 categories. Use search below to filter by title or click a category or tag to filter by tag or category.
Categories:
Tags:
Zero-trustSpiffeVaultSigstoreDockerSLSAGitHubGitHelmKubernetesTraefikTerraformsshReactNext.jsHexoBlogMarkdownNginxElasticsearchWebTLSLetsencryptHTTP/2WindowsRaspberry PiraspbiantestTDDbenchmarkconcurrencyparallelismbootChocolateyGradleJavaHTML5PWASEOPerformanceVirtualBoxAngularNode.jsazurehaproxysynologyvagranthyper-vBDDJasmineMochaKarmaPuTTYDebianpacker.ioChaiGruntSinonnpmJenkinsMSBuildMSpecOpenCoverNuGetArchitecturec#CQRSDesign patternsFluent SecurityJSONKnockoutJSMicrosoftPowerShellWindows 8Windows PhoneWindsorMVVMMVC3SecurityEntity FrameworklinqvhdConvincingElevator pitchSoftskillsAMDjQueryNcqrsdiskpartvdiskDDDFakeItEasyUnittestingDependency InjectionKinect
Stories
Writing modular JavaScript without polluting the global namespace
Marco Franssen /
Most of you have already seen a lot of spaghetti JavaScript code. One of the reasons you are reading this article will probably be, you don't want to make the same mistakes as others have done. So let's make the next step and stop polluting the global JavaScript namespace. Why is it bad to have all your script code available at global level? First of all you can possibly get a lot of errors when using modules developed by others, because you used the same names for you variables etc. The seco…