968 reputation
46
bio website
location
age
visits member for 3 years, 2 months
seen 2 days ago

2d
comment Dismissing the viability of implementing Microsoft Silverlight-based applications - a premature decision being made too early?
Imagine, five years from now even trying to hire someone to work on a Silverlight project that needs some maintenance or features modified or bugs fixed. Who's going to even still know it or much less be proficient at it. What top developer is going to want to invest any of their time in Silverlight? The date Microsoft officially drops it should be the end of a long transition away from it, not the beginning of a transition away from it. That means you start the transition now.
2d
comment Dismissing the viability of implementing Microsoft Silverlight-based applications - a premature decision being made too early?
There's no reason to stop using something today that already works. But, there's every reason to not invest another cent in that technology. And, yes that would mean that you start transitioning things over to HTML rather than continue to invest in a Silverlight implementation if you expect the use of the application to last very long (e.g. longer than Silverlight). It sounds like you are trying to convince yourself that it's perfectly fine to keep developing in Silverlight for a number of additional years because the end is not near. That, I think, is a fool-hardy decision.
2d
comment Dismissing the viability of implementing Microsoft Silverlight-based applications - a premature decision being made too early?
I have personally never, ever understood why anyone would invest in a solution based on a Microsoft-only technology such as Silverlight when mobile is often important and it's been clear for a long time that the future here is HTML5 and beyond and today's capabilities can solve many problems and it can be generally done cross platform. You seem to be looking for reasons to stay with Silverlight for longer. I could never see reasons to have even started with it in the first place and with it's now certain demise, there should be even more reasons to steer clear.
Nov
21
comment When to use AJAX
Your question is actually an interesting question, but it was doomed to be marked "primarily opinion-based" because of how you asked it. Instead of "who loves what", you need to ask things like "what are the programming and user advantages and disadvantages of using ajax to update a page versus loading a new page". That then tries to take so much opinion out of the question and asks for concrete benefits/drawbacks of each approach. In addition, you really need to frame the question in terms of a specific type of page or action because there's no single right answer for all uses.
Nov
19
comment how can I minimize my ajax calls to the server while creating a dashboard
Yeah, if you have buggy code, you app won't work - all you have to do is write code that works. There's no inherent reliability issue with distributing data to different parts of your app without making separate Ajax calls. If you are implementing it like a cache, then you may need to implement cache expiration so you get fresh results when you want fresh results.
Nov
19
comment how can I minimize my ajax calls to the server while creating a dashboard
You can minimize the number of Ajax calls by supporting on your server one Ajax call that retrieves all the info you need so only one roundtrip is needed to fetch all the data. If you need to share this info among completely separate modules, then you will have to make something like one central data manager which the modules will get their data from and the one central data manager will actually get the data or return the cached data.
Nov
10
answered How to debug minified javascript on production?
Nov
3
comment Node.js, Client side web cache
Just keep in mind that clients are notoriously bad servers (unreliable uptime, unknown availability, typically slow upload speeds). Yes, of course, you can code anything using a persistent connection like a WebSocket. Just because you can doesn't necessarily mean it's the best design choice, but you haven't shared enough particulars for us to do more than comment that it's highly unusualfor typically sound reasons (servers are better at being a central cache than clients are). Obviously, there are client-side cache systems like the old Napster or BitTorrent so it can be done.
Nov
3
comment Node.js, Client side web cache
You're still referring to Client 1, Client 2, Client A and Client B. Are there four clients involved here? And, are you trying to have one client get cached data from another client, but via a connection through the node server? I have no idea why you'd do that - why not just put a cache in your node server so you can control exactly what should be cached, control it's lifetime and cache validity and easily serve it to any client of interest?
Nov
2
comment Node.js, Client side web cache
What problem are you actually trying to solve? It isn't clear what you want to accomplish? Also your question refers to Client 1, Client 2, Client A and Client B. That seems very confusing.
Oct
5
comment Is JavaScript safe?
Much of the web doesn't work with full features without javascript enabled. The wide majority of the public is perfectly fine with any security aspects of javascript being enabled and it enables a much more functional web. So, unless you are building a site that is targeted at the minor portion of users that runs with javascript off, ignore them. I would NOT try to find any wording that tries to convince them to turn javascript on as that element is doing what they want and you can't change their minds. Just tell them that they must have javascript enabled in order to use your web site.
Sep
2
awarded  Yearling
Aug
25
comment What is the “best practice” for converting an external API's data structure?
Again, this is too generic a question. The app should structure its data in what makes the most sense for the app. There are many considerations that go into determining what makes the most sense. How the data must be organized for communicating with an API is only one of those considerations. How the data is used within the app is likely more important, but is just yet another consideration. How the data is stored persistently (if stored persistently) is yet another consideration, security might be another consideration and so on...
Aug
25
comment What is the “best practice” for converting an external API's data structure?
What do you mean "where it should be handled"? The consumer of the API constructs the arguments to an API function themselves. The implementor of the API processes the arguments as the specific implementation sees fit. I guess I don't understand what question you're asking. I'm thinking you need to provide an explicit example that shows several options you might be asking about.
Aug
25
comment What is the “best practice” for converting an external API's data structure?
This seems like far too generic a question. The right structure for sending data to an API depends upon a whole lot of things that are specific to the data, the application, how the data is normally consumed, how the data is transmitted and the specific API function, etc... For example, a Javascript API takes arguments and objects with properties, but a REST API requires most things in string form which may mean JSON.
May
30
revised Image caching when rendering the same images on different pages
Fix spelling in title
May
30
answered Image caching when rendering the same images on different pages
May
30
suggested suggested edit on Image caching when rendering the same images on different pages
May
12
comment JavaScript strict mode compatibility
The only case I can think of is if you're relying on something that is only true in strict mode (such as this === undefined in a regular function call) or relying on something causing an error in strict mode that doesn't cause an error in non-strict mode. Other than those odd things, yes you are correct that strict mode is more restrictive so normal code written in strict mode should work fine in non-strict mode.
May
5
comment How to make your JavaScript private?
If you want to require login for every user of your webpage, this will keep people who don't have the login credentials from using your website.